MerginMaps / MerginMaps/qgis-plugin
Improve error handling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 20
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
In case we have sync failure there is quite generic (and misleading) error message.
In this particular use case we get 504 from backend (on push finish) which is rare but valid situation when request takes too long to finish and it will never succeed. It can be even some link to docs for troubleshooting cases like this one.
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
Review the sync-failure path for the push-finish request and the generic error shown in the attached example. Reproduce the reported backend 504 if possible, then define an actionable message for that timeout case, including a troubleshooting documentation link if appropriate; confirm other sync failures still receive suitable handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100