onecrayon / onecrayon/api.ashes.live
Bug: fails to catch errors when updating user releases with existing release IDs
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 7
- Avg merge
- 7h 39m
- Merged PRs (30d)
- 1
Description
Error log:
sqlalchemy.exc.IntegrityError: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "idx_17083_primary"
DETAIL: Key (user_id, release_id)=(2655, 31) already exists.
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 by tracing the user-release update path described in the title and reproduce the SQLAlchemy IntegrityError for an existing release ID. Determine how duplicate (user_id, release_id) entries are expected to be handled, then add or update coverage for that case and verify the error is handled without violating the PostgreSQL uniqueness constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python, sqlalchemy
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100