MerginMaps / MerginMaps/db-sync
Network issues may freeze sync
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
It seems that mergin python client does not have any timeouts set. In case of a temporary network connection issue, the sync daemon may freeze and hang forever. It would be good to come up with a timeout, but not too short that could prematurely kill correct requests (e.g. push finish with a lot of data)
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 files or tests are named. Start by locating the Python client’s network request calls and the sync daemon entry point, then inspect how requests behave when connectivity is interrupted. Done means temporary network failures no longer hang synchronization indefinitely while long data pushes can still complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100