MerginMaps / MerginMaps/mobile
Better handle network issues
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Sometimes users are getting failures when downloading data:
- "Software caused connection abort."
- "Connection closed."
It seems these happen when there are network issues - and they may happen after few minutes after a request for a file (but seen a failure reported in logs after 2 hours since the request!)
We should try to be more resilient to such errors, especially if there are a few GB of data to download. Maybe we should be able to recognize a half-downloaded project and continue where the download got stuck.
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 locating the mobile app's data-download handling and examining how connection-abort and connection-closed failures are reported. Investigate whether a partially downloaded project can be recognized and resumed, including failures after long transfers; done means large downloads tolerate these network interruptions or resume without restarting.
Written by the indexing model from the issue text.
Assessment
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100