feat: add retry with exponential backoff and progress feedback (#12)#20
Open
feat: add retry with exponential backoff and progress feedback (#12)#20
Conversation
- Add retry loop with max 5 attempts in initiate_session - Exponential backoff: 2s, 4s, 8s, 16s between attempts - Emit connection_progress event with attempt number and status - Emit connection_error events with descriptive messages for each failure - Generate new ephemeral keys for each retry attempt - Add 60s timeout for ACK response - Provide clear error messages to users about connection failures This implements issue #12 to improve user experience when I2P tunnels are degraded. Users now see progress updates and the app automatically retries with increasing delays instead of failing immediately.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature: Add retry with exponential backoff and progress feedback (#12)
Closes #12
Problem
When I2P tunnels are degraded or the peer is temporarily unavailable,
initiate_sessionfails immediately with a generic error. This results in:This is particularly problematic on I2P, where tunnel establishment can take 30-60s and tunnels often degrade temporarily.
Solution
Implement retry with exponential backoff and progress feedback:
Retry loop with exponential backoff:
Progress events:
connection_progress: Emitted before each attempt withattempt,max_attempts, andstatusError events:
connection_error: Emitted after each failed attempt with descriptive messageTimeouts:
Clear final error:
Implementation details