-
Notifications
You must be signed in to change notification settings - Fork 407
Wake background-processor on async monitor update completion #2052
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
Comments
Note to self, starting point branch with logging: 2023-02-better-chain-monitor-logging |
It would be great if this new future is broad enough that the 100ms sleeper future in the LDK background processor could be removed (or at least default to a much higher value, like once a minute). Even though we don't use LDK's background processor directly, it would be a strong signal to us that LDK has confidence in its provided mechanisms for waking the background processor when needed, and would thus give us the confidence to remove our process events timer downstream. |
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wakt it using the new multi-`Future`-await `Waier`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
If the `ChainMonitor` gets an async monitor update completion, this means the `ChannelManager` needs to be polled for event processing. Here we wake it using the new multi-`Future`-await `Sleeper`, or the existing `select` block in the async BP. Fixes lightningdevkit#2052.
Probably need some kinda future like we have for ChannelManager persistence. We should also improve the logging in monitor persistence.
The text was updated successfully, but these errors were encountered: