Conversation
The lib is now async-only and we use the new high level API. There seems to be a bug in SetCommandResponder. Reported here: lextudio/pysnmp#230
vincentbernat
force-pushed
the
fix/pysnmp7
branch
from
2a9489e to
89d263c
Compare
We need a loop, otherwise we get blocked forever. There is still warnings about pending tasks: ``` task: <Task cancelling name='Task-586' coro=<AsyncioDispatcher.handle_timeout() running at /home/bernat/code/free/snimpy/.tox/py314/lib/python3.14/site-packages/pysnmp/carrier/asyncio/dispatch.py:66> wait_for=<Future cancelled>> Task was destroyed but it is pending! task: <Task cancelling name='Task-607' coro=<AsyncioDispatcher.handle_timeout() running at /home/bernat/code/free/snimpy/.tox/py314/lib/python3.14/site-packages/pysnmp/carrier/asyncio/dispatch.py:66> wait_for=<Future cancelled>> Task was destroyed but it is pending! task: <Task cancelling name='Task-615' coro=<AsyncioDispatcher.handle_timeout() running at /home/bernat/code/free/snimpy/.tox/py314/lib/python3.14/site-packages/pysnmp/carrier/asyncio/dispatch.py:66> wait_for=<Future cancelled>> Task was destroyed but it is pending! task: <Task pending name='Task-4' coro=<AsyncioDispatcher.handle_timeout() running at /home/bernat/code/free/snimpy/.tox/py314/lib/python3.14/site-packages/pysnmp/carrier/asyncio/dispatch.py:66> wait_for=<Future pending cb=[Task.task_wakeup()]>> Task was destroyed but it is pending! task: <Task pending name='Task-720' coro=<AsyncioDispatcher.handle_timeout() running at /home/bernat/code/free/snimpy/.tox/py314/lib/python3.14/site-packages/pysnmp/carrier/asyncio/dispatch.py:66> wait_for=<Future pending cb=[Task.task_wakeup()]>> Task was destroyed but it is pending! task: <Task pending name='Task-874' coro=<AsyncioDispatcher.handle_timeout() running at /home/bernat/code/free/snimpy/.tox/py314/lib/python3.14/site-packages/pysnmp/carrier/asyncio/dispatch.py:66> wait_for=<Future pending cb=[Task.task_wakeup()]>> ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snimpy was broken since quite a time with more recent versions of PySNMP. PySNMP 6 did remove the oneliner API we relied upon, but PySNMP 7 reintroduced it. There other small API changes, notably all methods are using the snake case. The update is not too invasive. A commit also update the build system to be a bit more modern.
Fix #111.