We have a simple test that verifies the Sentry SDK is capturing Flask errors because we had some configuration/PyPy issues in the past:
https://github.com/getsentry/snuba/blob/fd44ec8880240575ee2cb05bfc87e4cfd1d0e853/tests/test_api.py#L928-L936
As of this writing we don't pin the sentry-sdk version:
https://github.com/getsentry/snuba/blob/fd44ec8880240575ee2cb05bfc87e4cfd1d0e853/setup.py#L80
The test started failing because it seems that as of 0.3.7 (I tried 0.3.6 and wasn't able to reproduce the issue) the transport is being called twice for the same exception, causing the number of reported issues to be 2 instead of 1.
Maybe this is a false alarm but I think our integration is relatively simple so this may be signs of a larger issue?
We have a simple test that verifies the Sentry SDK is capturing Flask errors because we had some configuration/PyPy issues in the past:
https://github.com/getsentry/snuba/blob/fd44ec8880240575ee2cb05bfc87e4cfd1d0e853/tests/test_api.py#L928-L936
As of this writing we don't pin the
sentry-sdkversion:https://github.com/getsentry/snuba/blob/fd44ec8880240575ee2cb05bfc87e4cfd1d0e853/setup.py#L80
The test started failing because it seems that as of
0.3.7(I tried0.3.6and wasn't able to reproduce the issue) thetransportis being called twice for the same exception, causing the number of reported issues to be2instead of1.Maybe this is a false alarm but I think our integration is relatively simple so this may be signs of a larger issue?