Repository navigation
Stop returning raw internal errors to unauthenticated callers #184
Description
Background
The global error handler at src/api.ts:1005-1008 responds with res.status(500).json({ error: err.message }). Prisma and pg errors carry table names, column names and constraint names, and sometimes connection details; src/rpc.ts:277 throws with JSON.stringify(resp) embedded. Any unhandled path hands that to whoever asked.
Acceptance criteria
- 500 responses return a fixed message plus a generated correlation id
- The full error, with that id, is still logged server-side
- Deliberate 4xx responses keep their messages
- A test forcing
new Error('relation "token_transfer" does not exist')asserts the body does not contain that text — fails onmain
Drips Wave · Complexity: Easy · 100 points
How this repo is laid out
Wraith is a Soroban incoming-transfer indexer: it fills the gap Horizon leaves for SAC/SEP-41 token events by recipient address. Roughly 14k lines under src/, REST + GraphQL + WebSocket, Postgres via Prisma, deployed on Render.
- Unit tests are jest (
src/**/__tests__,tests/*.test.ts), with a coverage gate. - Integration tests are vitest (
tests/integration/,vitest.integration.config.ts, Docker). - Don't mix the two runners in one file.
Known state of main before you start
tsc --noEmit and the unit suite are green. The Integration tests CI job is red, and so is Load test — both predate this batch. Open PRs #177 and #178 address them. If the integration job is red when you open a PR, that is not your fault; say so in the PR and carry on.
Four modules are shipped, closed as done, and imported by nothing: src/indexer/checkpoint.ts, src/ingest/reorg.ts, src/middleware/opa.ts, and src/api/candles.ts + src/workers/ohlc-refresh.ts. So the live indexer today has no reorg handling and no atomic checkpointing, despite both features being closed. Two issues below start unpicking that — don't assume a closed issue means a wired feature.
Ground rules
- Every PR needs a test that fails before the change and passes after, unless the issue says otherwise.
- Don't widen a Prometheus label to something unbounded — addresses and contract ids must never become label values.
- Nothing may log or return a raw database error, a connection string, or a provider URL.
- Don't reformat a file you're changing. A diff that is 90% whitespace hides the 10% that matters.
Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk
Activity
RikaTech2006 commentedon Sep 25, 2026
@RikaTech2006 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @RikaTech2006 to this issue.
funds0033-cmyk commentedon Sep 26, 2026
@funds0033-cmyk has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @funds0033-cmyk to this issue.
drips-wave commentedon Sep 26, 2026
Congratulations, @RikaTech2006! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @RikaTech2006: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
fix(api): stop leaking raw internal errors to callers (#184) (#200)
drips-wave commentedon Oct 19, 2026
This issue has been completed by @RikaTech2006 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @RikaTech2006: You earned 100 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Merge PR #225: derive the native SAC defaults from the SDK, and fix t…