[bug] monitor-events sys.excepthook issue when using keyboard interrupt (ctrl-c) on a Python 3.10 runtime #475
Comments
|
confirming for 3.9 as well on WSL2 |
digimaun
pushed a commit
that referenced
this issue
Mar 11, 2022
* Automate resource generation for central tests. If the resource values are provided in the configuration file, they will be used. Otherwise, new resources will be created to run the tests. Within a given testing resource group, * a storage account will be created to be used for all the central tests * a separate central app will be created for each test and retrieving all possible central app values * the resources will be deleted once the tests are done. * Specifically, these configuration variables can be safely removed: * azext_iot_central_app_id * azext_iot_central_primarykey * azext_iot_central_scope_id * azext_iot_central_token * azext_iot_central_dns_suffix * azext_iot_central_storage_cstring * azext_iot_central_storage_container * In addition, fixing sys.excepthook error in issue #475 by specifying which loop is to be closed.
|
Closing since this was resolved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
At least on a Python 3.10 runtime using
az iot hub monitor-events, sys.excepthook errors are shown on keyboard interrupt. This was observed on a homebrew based install.To Reproduce
Steps to reproduce the behavior:
0.12.0,0.12.1) on a Py 3.10.x based Azure CLI install. Run monitor-events and input keyboard interrupt. Observe errors.Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
MacOSbash2.31.00.12.0,0.12.1Python 3.10.xThe text was updated successfully, but these errors were encountered: