-
Notifications
You must be signed in to change notification settings - Fork 541
Multiprocessing integration #291
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
@rouge8 @crepererum can you clarify whether you want this because of celery or something else? After creating this issue I discovered that Celery issues need to be tackled separately. |
Dask is able to use local processes as a local backend, and it would be really helpful to at least get the queues flushed properly ( |
@crepererum could you open a new issue wrt Dask support? The more I think about this (multiprocessing) support the more I thikn it's an A/B problem. |
I was reviewing the open issues while migrating away from the old raven library. :) We have some code that uses multiprocessing, but I haven't compared behavior with raven and sentry_sdk or anything yet. |
A change in Apache Airflow (to use os.fork, and thus the recommended It would be nice to have a way to explicitly call the Sentry exit handler. https://issues.apache.org/jira/browse/AIRFLOW-6569 /cc @tiopi |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
are there any workarounds for the lack of unhandled exception capture? All I can think of is a decorator, ie
Downside is that all exceptions are reported as handled. |
Hey @davegravy This looks solid. For the problem with "handled" you could something like we do in our integrations to have a custom |
We do support
fork()
in general, but the multiprocessing module has some quirks.atexit
does not get called, so events get lostAn integration should fix both. We should also consider Billard, a fork of mulitprocessing here. If we manage to properly hook into both versions, we can catch some startup errors in Celery as well.
If you're interested in this, please give this post a 👍 so it's easier to track.
The text was updated successfully, but these errors were encountered: