Decide Scheme exception pickup translation support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Support automatic ingestion of uncaught Scheme exceptions through a pickup component.
A Scheme runtime can write an exception report when a thread raises an uncaught SRFI-12 condition. The pickup component should:
- discover and attach the generated report
- translate the condition type, message, metadata, thread information, and stack frames into Sentry's standard error event format
- submit the translated event for ingestion
The Scheme program should not need to construct a Sentry payload or integrate a dedicated Scheme SDK. The requested experience is:
Scheme exception report → pickup and translation → Sentry ingestion
Initial scope is CHICKEN Scheme 5 with SRFI-12 conditions. The report format can be defined as part of the implementation because the producer can pre-process the data into the required shape.
Requested by David Quintas.
--
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating existing pickup components and the standard error event format used for ingestion. Define the CHICKEN Scheme 5 report shape and trace how condition data, thread information, and stack frames can be translated and submitted; done means an uncaught SRFI-12 condition reaches Sentry without a Scheme SDK or manually constructed payload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100