-
-
Notifications
You must be signed in to change notification settings - Fork 167
Insights: getsentry/sentry-rust
Overview
-
- 4 Merged pull requests
- 0 Open pull requests
- 3 Closed issues
- 4 New issues
Could not load contribution data
Please try again later
4 Pull requests merged by 2 people
-
fix(actix): capture only server errors
#877 merged
Aug 6, 2025 -
build(panic): Fix build without other dependencies
#883 merged
Aug 6, 2025 -
feat(types): add Response context
#874 merged
Aug 4, 2025 -
docs(tower): suggest reordering layers when using axum
#881 merged
Aug 4, 2025
3 Issues closed by 1 person
-
Don't capture client errors in Actix Web integration
#876 closed
Aug 6, 2025 -
Binding tower layers in wrong order causes a memory leak
#695 closed
Aug 4, 2025 -
sentry-tracing: `SentryLayer` ignores `event_filter` if `event_mapper` is set
#630 closed
Aug 4, 2025
4 Issues opened by 3 people
-
Better handling of HTTP failures
#884 opened
Aug 6, 2025 -
Support and send Client Reports
#882 opened
Aug 4, 2025 -
tracing::span "message" field should NOT be empty during span creation
#880 opened
Aug 4, 2025 -
Sentry span.description requires setting "message" field
#879 opened
Aug 4, 2025
1 Unresolved conversation
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
feat(tracing): send both breadcrumbs and logs by default
#878 commented on
Aug 4, 2025 • 0 new comments