-
Notifications
You must be signed in to change notification settings - Fork 99
Exceptions are ignored #31
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
Comments
`#usr/env/bin python def process_packet(packet
packet.accept() queue = netfilterqueue.NetfilterQueue() I was returned with the same error as posted in the query, i.e. |
I made an error in the code, issue resolved. |
Hey, bro need your help!!! I am facing sort of same situation, can you help me out with the error with the netfilterqueue library:-- |
@YuvrajSingh-16, I think a workaround during development might be to put a blanket try/catch at the top level in your callback function and use the |
hey guys i am facing the same error I think you guys are students from zsecurity.How did you solve the error??@Zat-DB @strictlymike @YuvrajSingh-16 |
I am having the same problem. I am here scratching my head. My code looks good but I have the same error. Any help would be appreciated.
Terminal Output: |
Propagate exceptions raised by the user's packet callback -- fixes #31, #50 Warn about exceptions raised by the packet callback during queue unbinding Raise an error if a packet verdict is set after its parent queue is closed set_payload() now affects the result of later get_payload() -- fixes #30 Handle signals received when run() is blocked in recv() -- fixes #65
When an exception is raised in my callback, I simply see a message like this one:
This makes troubleshooting painful. Is there a safe way for you to allow the exception to terminate the script with the normal stack trace? Short of that, maybe a constructor argument or other mutator to give developers the ability to opt for more detailed exception information?
I'd like to be more helpful but at a glance I can't tell where these exceptions are being handled and silenced. If you can point me to it, I'll be happy to take a crack at a PR.
The text was updated successfully, but these errors were encountered: