Ivana Kellyer

So as said [in the original thread](https://github.com/getsentry/sentry-python/issues/2699#issuecomment-1946305490) I'm thinking this has to do with the SDK spawning a new thread by default in 1.40+ and possibly hitting some thread limits...

Hey folks, thanks for following up. @gksb88 Which SDK version did you upgrade from? Are you creating your own threads in your app? @kerenkhatiwada According to the OP, > Rolling...

@gksb88 Since you said you started seeing this after upgrading to 1.43.0, can you confirm that you didn't encounter the issue on 1.40.3? If that's the case, going back to...

@gksb88 The SDK spawns an additional thread in ~1.40, but we were already utilizing threads before that, see https://github.com/getsentry/sentry-python/issues/2741#issuecomment-2058833103: > The SDK itself should normally spawn about ~5 threads max...

Hey @anton-demydov-zoral, SDK 1.x is not developed anymore outside of security fixes. Can you try with the latest 2.x [release](https://github.com/getsentry/sentry-python/releases) to see if this is also an issue in 2.x?...

@grigi Awesome, thanks for giving this a shot! 🚀 We definitely will need tests for this -- I'd look at how the tests for similar integrations (like ARQ for instance)...

Hey @yuqiuwen, thanks for writing in. I can't reproduce the issue. Here's my small Flask app: ```python import sentry_sdk from flask import Flask class AuthException(Exception): pass sentry_sdk.init( dsn=, debug=True, ignore_errors=[AuthException],...

@yuqiuwen `before_send` is another way to do it, great that that works for you. I'd still like to understand why `ignore_errors` doesn't though, but for that I'd need a full...

> Maybe I see , because of logging the error, is right? if i don't log the error, it works well. > > ```python > @app.errorhandler(AuthException) > def handle_auth_error(e): >...

It probably got truncated by some part of the system because it was too long. Not sure off the top of my head if this is the SDK or the...