getsentry / getsentry/sentry-python
Adhere to user callback error spec
Open
Python
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 669
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 213
Description
Have a look at the parent project and/or develop docs.
We should be already wrapping most cases; there might be improvements necessary when it comes to emitting client reports.
Contributor guide
Research direction
Start by reading the parent project and the develop docs referenced in the issue, then compare the SDK's current user-callback wrapping and client-report behavior with that specification. Done means the remaining callback cases are handled as required and client reports are emitted consistently; the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100