-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am getting a Windows error (WinError 995) on a number of pywbemcli commands #690
Comments
This seems to be the error reported here: prompt-toolkit/python-prompt-toolkit#1023 (comment). They have opened a Python bug against 3.8, which changed the type of event processor to async. The prompt-toolkit issue suggests that changing the type of event processor back may address the issue. The 'blessed' project also encountered this (issue jquast/blessed#121) and they relate it to using prompt-toolkit>=3.0. I think we should first try to pin prompt-toolkit to <3.0. NOTE: This was eventually tied back to python bug https://bugs.python.org/issue39010 |
…ror 995. Details: * Pinned prompt-toolkit to <3.0 on Python 3.8 on Windows to avoid WinError 995. (See issue #690) * In requirements.txt, clarified the reasons for the other version constraints on prompt-toolkit. Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
@FarmerMike252 Mike, I have a PR #696 that I think fixes this, but it requires your confirmation. --> Could you please verify that the error is gone on Windows with Python 3.8 when using pywbemcli from the branch of that PR? To do that, you need to reinstall pywbemtools using that branch, so it downgrades prompt-toolkit to <3.0. Alternatively, you can do that yourself without using that branch: Once that is confirmed, I can roll it back into 0.7.1 and release that. |
I have run two of my CLI scripts, including the one that had errors in yesterday's SM Lab meeting. Both scripts ran clean. So, I believe the problem is successfully fixed. |
Ooops! I didn't realize I was not supposed to close the issue. |
NP, Mike. Thanks for testing it! I'll roll back the PR to 0.7.1 then and we'll discuss releasing it in our call today. |
…ror 995. Details: * Pinned prompt-toolkit to <3.0 on Python 3.8 on Windows to avoid WinError 995. (See issue #690) * In requirements.txt, clarified the reasons for the other version constraints on prompt-toolkit. Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
…ror 995. Details: * Pinned prompt-toolkit to <3.0 on Python 3.8 on Windows to avoid WinError 995. (See issue #690) * In requirements.txt, clarified the reasons for the other version constraints on prompt-toolkit. Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
…ror 995. Details: * Pinned prompt-toolkit to <3.0 on Python 3.8 on Windows to avoid WinError 995. (See issue #690) * In requirements.txt, clarified the reasons for the other version constraints on prompt-toolkit. Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
I am getting the WinError 995 error on some of my pywbemcli commands. The command produces the expected output but then I get the following error message:
Unhandled exception in event loop:
File "c:\users\farmermike\appdata\local\programs\python\python38-32\lib\asyncio\proactor_events.py", line 768, in _loop_self_reading
f.result() # may raise
File "c:\users\farmermike\appdata\local\programs\python\python38-32\lib\asyncio\windows_events.py", line 808, in _poll
value = callback(transferred, key, ov)
File "c:\users\farmermike\appdata\local\programs\python\python38-32\lib\asyncio\windows_events.py", line 457, in finish_recv
raise ConnectionResetError(*exc.args)
Exception [WinError 995] The I/O operation has been aborted because of either a thread exit or an application request
Press ENTER to continue...
I press enter and can continue with my script, so this is not a high priority, but it would nice to get rid of the error message.
The text was updated successfully, but these errors were encountered: