MerginMaps / MerginMaps/db-sync
Keep sync running if some connections have a problem
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Right now, if there are multiple connections defined and one of them fails to sync for some reason, the whole sync stops. It would be nice if db-sync tool would be less strict and it could tolerate some failing connections.
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 in the issue. Start at the db-sync tool's multi-connection synchronization entry point, trace how a connection failure is handled, and verify that later connections still sync while the failed one is reported without aborting the run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100