Make feerates resolution asynchronous #654
Merged
Conversation
This file contains 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
t-bast
previously approved these changes
May 30, 2024
Instead of waiting for feerates to be available before processing any channel command, we just pass the `StateFlow` to the `ChannelContext` and will attempt to get feerates only when needed. If feerates are not available, the `ChannelState.process` function will hang. Previously, the hanging would have happened in the `Peer`.
t-bast
approved these changes
May 31, 2024
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.
Instead of waiting for feerates to be available before processing any channel command, we just pass the
StateFlowto theChannelContextand will attempt to get feerates only when needed.If feerates are not available, the
ChannelState.processfunction will hang. Previously, the hanging would have happened in thePeer.