Network issues may freeze sync

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, networking

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.

Description

bug

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)

Dominant language
Python
Stars
53
Forks
24
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/db-sync

All issues in MerginMaps/db-sync

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.