stackabletech / stackabletech/cockpit
Raw upstream error messages returned to the client
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 22h 6m
- Merged PRs (30d)
- 12
Description
File: src/lib/server/trino/queries.ts:176
Trino error messages are stored verbatim in query.error and surfaced through buildSnapshot.error to the client. Trino errors may expose schema details, table names, or internal query plans. These should be classified (query error vs. infrastructure error) and sanitised before being surfaced to users.
Contributor guide
No contributing guide indexed for this repository
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 at src/lib/server/trino/queries.ts:176 and trace how Trino errors in query.error reach buildSnapshot.error and the client. Define the query-error versus infrastructure-error classification and sanitization rules from that flow. Done means raw schema details, table names, and internal query plans are not surfaced to users while the two error classes remain distinguishable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100