Network errors are not retried during polling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 7h 43m
- Merged PRs (30d)
- 17
Description
Network errors during polling (such as server closing the connection) cause immediate failure without retry.
According to RFC 8628 Section 3.5: https://www.rfc-editor.org/rfc/rfc8628#section-3.5
On encountering a connection timeout, clients MUST unilaterally reduce their polling frequency before retrying. The use of an exponential backoff algorithm to achieve this, such as doubling the polling interval on each such connection timeout, is RECOMMENDED.
Currently, network errors like io.EOF make the entire authentication flow fail, even when these are transient issues that could be resolved by retrying.
Contributor guide
No contributing guide indexed for this repository
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 device-authorization polling flow and the handling of network errors such as io.EOF. Compare the current behavior with RFC 8628 Section 3.5, then define completion as retrying transient connection failures while reducing the polling frequency, preferably with exponential backoff, instead of failing the authentication flow immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100