Open MSzalowski opened 1 week ago
I decided to temporarily disable the reporting of this error in order not to exceed the sentry limit. The reason behind this decision is that the thrown exception means that before the client finished sending the data, there was a timeout that terminated the sending. This is intentional behavior and does not affect normal use of the application, and only occurs during stress testing.
I'll keep this issue as open and on To do
to provide the solution instead of the workaround for reporting.
Context & versions
Steps to reproduce
Sentry reports killed thread by timeout manager on Haskell backend.
Actual behavior
Sentry reports killed thread by timeout manager on Haskell backend.
Expected behavior
Timeout shold be investigated and fixed.