Add retry mechanism for default online style fetches that fail due to network errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Locate the application code that updates the displayed map from the offline fallback to the online style, then inspect how the desktop window online event triggers the fetch. Add retry behavior for online-style fetches that fail from unavailable internet access, and verify that a failed fetch is retried when connectivity is actually restored.
Written by the indexing model from the issue text.
Description
We have some application code that attempts to update the displayed map from the offline fallback to the online style when the network is connected again. However, network being "connected" does not necessarily mean that internet access is available and getting that information can be limited based on which APIs you have access to. For example, desktop uses the window online event, which only reflects when you regain access to a network but makes no guarantees about access to the internet.
To my knowledge, fetch calls that fail due to lack of internet connection do so immediately i.e. no configurable timeout to wait for. Given this, I think it would make sense to set up a retry for the online style if that kind of failure does occur.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 digidem/comapeo-map-server
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
digidem/comapeo-map-server#80 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in digidem/comapeo-map-server
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#282 ·
-
bug P2 rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gabe-santana/arkdraw#25 ·
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#101 · 1 comment ·
Maintainers usually reply within 1 day