-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce OffersMessageFlow #3412
base: main
Are you sure you want to change the base?
Conversation
0972b33
to
e038951
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, I reviewed this offline with @shaavan. So there will be some changes to the OffersMessageFlow
trait parameterization to keep ChannelManager
specifics from leaking.
return Err(Bolt12SemanticError::UnsupportedChain); | ||
} | ||
|
||
let _persistence_guard = PersistenceNotifierGuard::notify_on_drop(self); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TheBlueMatt Do you know why we need the PersistenceNotifierGuard
here? This code sends an invoice for a refund (i.e., an inbound payment). IIUC, we don't persist pending_offers_messages
, so it seems we don't need it.
e038951
to
e1c3863
Compare
e1c3863
to
d5c244a
Compare
d5c244a
to
c07e7f6
Compare
Updated from pr3412.04 to pr3412.05 (diff): Addressed @jkczyz's (offline) comments. Changes:
|
4911f9f
to
9d0c511
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3412 +/- ##
==========================================
+ Coverage 89.72% 89.78% +0.05%
==========================================
Files 130 131 +1
Lines 107614 108190 +576
Branches 107614 108190 +576
==========================================
+ Hits 96559 97137 +578
+ Misses 8660 8659 -1
+ Partials 2395 2394 -1 ☔ View full report in Codecov by Sentry. |
9d0c511
to
b3c54ee
Compare
Updated from pr3412.06 to pr3412.07 (diff): Changes:
|
b3c54ee
to
3ba8ba5
Compare
3ba8ba5
to
189b2aa
Compare
To decouple offers and onion message-related code from `ChannelManager`, this commit introduces the `message_received` function in `Offer/OnionMessageHandler`. Currently, the function focuses on handling the retry logic for `InvoiceRequest` messages. Moving this responsibility ensures a cleaner separation of concerns and sets the foundation for managing offers/onion messages directly within the appropriate handler.
Since `ChannelMessageHandler`'s `message_received` function was solely used for handling invoice request retries. This function has been removed from `ChannelMessageHandler`, and the relevant code has been migrated to `OffersMessageHandler`'s `message_received`. This ensures invoice request retries are now handled in the appropriate context.
189b2aa
to
4818efe
Compare
This commit temporarily removes support for async BOLT12 message handling to enable a smoother transition in the upcoming refactor. The current implementation of async handling is abrupt, as it requires delving into the synchronous case and generating an event mid-flow based on the `manual_handling` flag. This approach adds unnecessary complexity and coupling. A later commit will introduce a new struct, `OffersMessageFlow`, designed to handle and create offer messages. This new struct will support async handling in a more structured way by allowing users to implement a parameterized trait for asynchronous message handling. Removing the existing async support now ensures a cleaner and more seamless migration of offer-related code from `ChannelManager` to `OffersMessageFlow`.
This commit introduces a new struct, `OffersMessageFlow`, to extract all offers message-related code out of `ChannelManager`. By moving this logic into a dedicated struct, it creates a foundation for separating responsibilities and sets up a base for further code restructuring in subsequent commits.
A new trait, `OffersMessageCommons`, is introduced to encapsulate functions that are commonly used by both BOLT12-related functionality and other parts of `ChannelManager`. This enables a clean transition of BOLT12 code to `OffersMessageFlow` by moving shared functions into the new trait, ensuring they remain accessible to both `ChannelManager` and the refactored BOLT12 code.
This commit introduces the `OffersMessageHandler` implementation for `OffersMessageFlow`, enabling direct access to offer-specific functionality through `OffersMessageFlow`. With `OffersMessageFlow` now serving as the source of `OffersMessageHandler` implementation, the implementation in `ChannelManager` is no longer needed and has been safely removed.
- This commit introduces a new struct, `AnOffersMessageFlow`, which generically implements `OffersMessageFlow`. - In subsequent commits, this struct will be utilized for documentation purposes.
- The _persistence_guard here was not serving any purpose, and hence can be removed in this refactoring.
1. This allow removing an extra function from commons, simplifying the flow trait.
4818efe
to
10b25f4
Compare
This PR introduces a new data structure to separate the functions and fields related to Offers Message from
ChannelManager
.The change ensures a clear separation of responsibilities for BOLT12 messages, improving modularity and maintainability.
TODO: