Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sentry integration and background tasks
See original GitHub issueDescribe the bug
Looking at the Sentry integration, a hub is created on request (‘http.lifecycle.request’ => _hub_enter) and removed at exit (‘http.lifecycle.response’ => _hub_exit).
If I understand this correctly, it means that if an exception occurs outside of the request, no Hub will be define and the exception won’t be caught by Sentry.
This can happen when running a long background_task from a request handler that has already returned a response.
Environment (please complete the following information):
- Sanic Version: 22.9.0
- Sentry SDK : 1.9.9
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Done 😃
ping me in that issue