Repository navigation
Conversation
…uMemoCache options, and implement RpcCircuitBreaker for timeout handling
|
@0xMegie Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This branch has not been deployed
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
1 participant
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.
closes #929 - useStreamCountdown now ticks on requestAnimationFrame and only re-renders when the displayed second changes, so the countdown lands on the second boundary instead of drifting behind a setInterval.
The public return shape is unchanged; DOM-ref updates from the issue are not included.
closes #924 - mapWithConcurrency accepts an optional requestsPerSecond option, enforced with a token bucket, so bursts of Horizon/RPC calls can be spaced out even when concurrency is low.
Callers that pass no options are unaffected.
closes #923 - LruMemoCache accepts { maxEntries, ttlMs } in its constructor, with ttlMs as the default TTL for set(). The numeric constructor form still works.
The caller that hardcodes 100 entries is not updated in this PR.
closes #922 - Adds RpcCircuitBreaker, which opens after 3 consecutive RPC timeouts and goes half-open after 30 seconds, so calls fail fast during an outage.
Non-timeout outcomes count as the endpoint being reachable and close the circuit.