Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Optimization]consider adding an API to query the channel synchronization progress. #534

Open
15168316096 opened this issue Feb 28, 2025 · 1 comment
Open

[Optimization]consider adding an API to query the channel synchronization progress. #534

15168316096 opened this issue Feb 28, 2025 · 1 comment

Comments

@15168316096
Copy link

When there are many channels, sending a-b-c paths requires waiting for the channel synchronization to be completed. At this time, it will be stuck for a long time. You may want to consider adding an API to query the channel synchronization progress.

Image
@15168316096
Copy link
Author

In addition, the speed of channel synchronization must be optimized.

@15168316096 15168316096 changed the title When there are many channels, sending a-b-c paths requires waiting for the channel synchronization to be completed. At this time, it will be stuck for a long time. You may want to consider adding an API to query the channel synchronization progress. consider adding an API to query the channel synchronization progress. Feb 28, 2025
@15168316096 15168316096 changed the title consider adding an API to query the channel synchronization progress. [Optimization ]consider adding an API to query the channel synchronization progress. Feb 28, 2025
@15168316096 15168316096 changed the title [Optimization ]consider adding an API to query the channel synchronization progress. [Optimization]consider adding an API to query the channel synchronization progress. Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@15168316096