Skip to content

fix: Handled is no longer set to false for blocking calls #4458

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.

Sign up for GitHub

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

Merged
jamescrosswell merged 2 commits into from
Aug 22, 2025
Merged

fix: Handled is no longer set to false for blocking calls #4458

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a43b87
fix(blocking-monitor): omit 'handled' flag for blocking call detectio…
jamescrosswell Aug 21, 2025
953597b
Update CHANGELOG.md
jamescrosswell Aug 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
fix(blocking-monitor): omit 'handled' flag for blocking call detectio… 
…n events (level: warning)

This resolves #XXXX. The 'handled' property is now omitted from the mechanism for blocking call detection events, so they are not treated as unhandled crashes in Sentry UI.
  • Loading branch information
@jamescrosswell
jamescrosswell committed Aug 21, 2025
commit 4a43b87679a7d9b09d1cf44e8739ed28f5e54f09
1 change: 0 additions & 1 deletion src/Sentry/Ben.BlockingDetector/BlockingMonitor.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,6 @@ public void BlockingStart(DetectionSource detectionSource)
Mechanism = new Mechanism
{
Type = "BlockingCallDetector",
Handled = false,
Description = "Blocking calls can cause ThreadPool starvation.",
Source = detectionSource.ToString()
},
Expand Down
Loading