MerginMaps / MerginMaps/db-sync
Crash when violating db constraints
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
DB Sync run crashes when it tries to sync data from MM to DB but the data are rejected because of violation of PG constraints.
Expected: we write error instead, not crash
Bug report from our customer.
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
No file or test is named. Start by reproducing a DB Sync run against PostgreSQL where incoming data violates a database constraint, then trace the sync error path. Done means the constraint violation is recorded as an error and the synchronization process does not crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100