db-sync service completely stop if db is unreachable
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
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.
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.
- Dominant language
- Python
- Stars
- 53
- Forks
- 25
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from MerginMaps/db-sync
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/db-sync#184 ·
-
Build in CI pipelinePossibly taken @varmar05 claimed this 8 days ago. Open
MerginMaps/db-sync#189 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
MerginMaps/db-sync#185 · 1 comment ·
-
db-sync enters an infinite drop/recreate loop when geodiff init fails on invalid source geometriesOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
MerginMaps/db-sync#182 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
MerginMaps/db-sync#181 · 2 comments ·
All issues in MerginMaps/db-sync
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
QuantEcon/lecture-python-programming#642 ·
Maintainers usually reply within 1 day
-
area/config area/profiles comp/cli needs-decision P3 sweeper:risk-compatibility type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#133697 ·
Maintainers usually reply within 1 day
-
enhancement needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vectorize-io/hindsight#5279 ·
Maintainers usually reply within 1 day