-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
tokio-console cannot show the pause status correctly #551
Comments
I need to check the API, because I don't remember how it's set up currently. But ideally the status would be sent as part of the regular updates which are pushed from the What do you think @hi-rustin? |
Do you mean we always push the paused state on updates? If we only push it once, then the new client will not get it if it tries to connect to the server after the server has been paused. |
A new client should always receive at least one update, which would indicate that the state is "Paused" in this case. |
Sounds good. I will try to add it. |
What crate(s) in this repo are involved in the problem?
tokio-console
What is the issue?
There are two Tokio Console instances connected to the same stream. If you pause the stream in one instance and the status cannot be displayed correctly in the other instance.
How can the bug be reproduced?
All steps execute under the git repo:
cargo run --example app
cargo run
cargo run
space
in one of the instancesLogs, error output, etc
No response
Versions
Possible solution
Perhaps we should include a new API to allow clients to check whether the stream has been paused.
Additional context
I believe the reason for this problem is that we only store the pause status on the client side. Therefore, there is no way to notify other instances to know the stream is paused.
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered: