-
Notifications
You must be signed in to change notification settings - Fork 339
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
V3 Index out of range #250
Comments
Please see my comment in README: 11 July 2020 - I'm planning on archiving gosnmp, as maintaining it is having too much of an effect on my work and personal life. I started the fork in March 2013 and I've been working on it ever since. At the moment I'm keeping it open so it can act as a central clearing house for issues and discussions around who is going to fork and maintain gosnmp. |
I'm posting to all open issues that we now have a community maintainer effort going. If this issue is still valid, please post an update. |
This happened today... Seems like it's the same issue.
|
Also something interesting... it appears that if i just simply retry it mitigates the issue
So the issue seems to stem from the packet being created by Just for clarity, the GOSNMPClient simply wraps
|
I am facing the same issue. Any workaround for this issue? |
I was unable to find a real workaround. Although I did add a simple retry in my app and that mitigated the issue. I found that this never seems to occur twice in a row. |
Note that this may be fixed by PR #443. There were two issues there that might be related:
|
I'm seeing the following panic,
line v3.go 437 is
which makes it seem like the
parseLength(packet[cursor:])
calculation is incorrect?The text was updated successfully, but these errors were encountered: