fix: Don't block on sending envelopes (ureq/curl transports) #701
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a followup to #546 (for #543):
Any transport is susceptible to #543, where sending too many events (or even potentially due to network hiccups) to Sentry can block. So the
thread::TransportThread
impl should similarly drop events instead of blocking, just as the similartokio_thread::TransportThread
began doing with the fix in #546.