-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Latest version of pyasn1 == 0.50 is breaking the pysnmp package. #438
Comments
Known issue. Either you manually downgrade pyasn1 to its 0.4.x releases, or switch to a fork that's actively maintained (like pysnmp-lextudio). Read #429 to learn more. |
It contains an incompatible change. See etingof/pysnmp#438.
You might close this issue if the solution worked. |
pyasn1 release 0.5.1 fixed the incompatibility, so you can close this issue now. New installation of pysnmp 4.x should resolve pyasn1 dependency to 0.5.1 by default and this issue won't appear again. |
Confirming what @lextm said, also fixed in 0.6.0 as well. This issue can be closed |
The latest version of pyasn1 released on April 20 2023 is breaking the pysnmp package.
snmp_walk command is failed.
++++++++++++++++++++++++++++++++
Working Version == pyasn1==0.4.8
+++++++++++++++++++++++++++++++++++
File "/data/users/jenkins/workspace/project/fss3/json-ci-snmp-sanity-2-py3/workspace_artifacts/testcase-framework-dir/test_framework/exec/.virtual-env-base-dir/test-engine-virtualenv-dir/lib64/python3.6/site-packages/pysnmp/carrier/asyncore/dispatch.py", line 46, in runDispatcher
use_poll=True, map=self.__sockMap, count=1)
File "/usr/lib64/python3.6/asyncore.py", line 207, in loop
poll_fun(timeout, map)
File "/usr/lib64/python3.6/asyncore.py", line 188, in poll2
readwrite(obj, flags)
File "/usr/lib64/python3.6/asyncore.py", line 123, in readwrite
obj.handle_error()
"/usr/lib64/python3.6/asyncore.py", line 108, in readwrite
obj.handle_read_event()
File "/usr/lib64/python3.6/asyncore.py", line 423, in handle_read_event
self.handle_read()
The text was updated successfully, but these errors were encountered: