MerginMaps / MerginMaps/db-sync
db-sync service completely stop if db is unreachable
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
When an error occurs, for example when db is unreachable, db-sync service completely stop and do not sync anymore after sleep time.
Note that it is possible to run dbsync using cron and option --single-run as a workaround.
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
Start by reproducing the failure with the database unreachable during the service's sleep interval, then trace the db-sync service entry point that handles recurring synchronization. Confirm the service continues syncing after the database becomes reachable again, while preserving the documented --single-run cron workaround.
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