Flows: improve error handling
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html
- Domain
- backend-api-design
Research direction
Start by reading the flow specification and the steps for processing a payment, especially “Revoke user wallet credentials.” Identify the payment errors covered by the current behavior and how the spec handles them. Done means the spec defines suitable behavior for different failure cases, including network timeouts and outgoing payments that fail due to low balance.
Written by the indexing model from the issue text.
Description
Currently, when processing a payment we run Revoke user wallet credentials when there is an error. Also in cases where it's just a simple network timeout, or for any reason creating an outgoing payment would fail (low balance?). We should dive deeper into the different possible errors and adjust the spec for it.
- Dominant language
- HTML
- Stars
- 608
- Forks
- 169
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from WICG/webmonetization
-
specification
Difficulty 1/5 Under an hour Newbie friendliness 78/100
WICG/webmonetization#813 ·
Maintainers usually reply within 3 days
-
specification
Difficulty 1/5 Under an hour Newbie friendliness 78/100
WICG/webmonetization#812 ·
Maintainers usually reply within 3 days
-
specification
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
WICG/webmonetization#811 ·
Maintainers usually reply within 3 days
-
specification
Difficulty 1/5 Under an hour Newbie friendliness 82/100
WICG/webmonetization#810 ·
Maintainers usually reply within 3 days
-
Update goals sectionOpenspecification
Difficulty 1/5 Under an hour Newbie friendliness 48/100
WICG/webmonetization#814 ·
Maintainers usually reply within 3 days
All issues in WICG/webmonetization
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Deltares/numba_celltree#100 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
hexlet-basics/hexlet-basics#968 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
kubernetes-sigs/scheduler-plugins#1031 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stratum-mining/sv2-tp#167 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
heysidhant/appvanish#3 ·