ReferenceConstraintException caught silently with no logging
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by reading the catch blocks in Appy/Services/ClientService.cs around line 105 and the similar pattern in Appy/Services/ServiceService.cs. Confirm how ReferenceConstraintException is converted to BadRequestException("Archive"). Done means both paths log the exception at warning level with the entity type and ID before conversion, while preserving the existing client response.
Written by the indexing model from the issue text.
Description
Description
ReferenceConstraintException is caught and silently converted to a BadRequestException("Archive") with no log entry. The original constraint violation context is discarded.
Location
Appy/Services/ClientService.cs(line ~105)Appy/Services/ServiceService.cs(similar pattern)
Risk
Constraint violations are invisible in logs, making it impossible to diagnose why archive/delete operations fail in production. Unrelated constraint errors (schema bugs, migration issues) get silently swallowed too.
Suggested Fix
Log the exception at warning level before converting it, including the entity type and ID. Consider providing a more specific error message to the client.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from Worly/Appy
-
bug llm generated low priority
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement llm generated low priority
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement llm generated low priority
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug llm generated low priority
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
enhancement llm generated low priority
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·