Skip to content

tokio-console does not display a error when console-subscriber <0.5.0 is used #650

@hasezoey

Description

@hasezoey

What crate(s) in this repo are involved in the problem?

tokio-console

What is the issue?

I recently re-installed tokio-console and had followed the documentation (which had not changed since my last time using it) to instrument my application, but i was stumped why it was never connecting.
After investigating the logs, it turned out the following was logged, but never actually displayed in the TUI:

ERROR tokio_console::conn: The server at http://127.0.0.1:6669/ does not support state streaming. Please update the console-subscriber to v0.5.0 or later version.

It would be way more intuitive if the TUI itself could display this error instead of just CONNECTING and RECONNECTING IN.

Another issue, which likely deserves its own issue report:
While this error is active, tokio-console somehow does not render anything until a key is pressed, leaving a blank screen (similar to what is described in #360)
Though i can only reproduce this on linux(konsole), not on windows(powershell).

PS: for anyone that may come across this as well and the error is not yet displayed on the TUI: when defining console-subscriber = "*" somehow cargo does not decide to use 0.5.0, but 0.4.1, even though console-subscriber is listed as new in the Cargo.lock (so it cannot just be that it inherited a old version)

How can the bug be reproduced?

Install tokio-console 0.1.14 and have your actual application have console-subscriber 0.4.1 installed.

Logs, error output, etc

I dont think the full log is necessary, but:

ERROR tokio_console::conn: The server at http://127.0.0.1:6669/ does not support state streaming. Please update the console-subscriber to v0.5.0 or later version.

Versions

├── console-subscriber v0.4.1
│   ├── console-api v0.8.1

Possible solution

Explicitly install console-subscriber at 0.5.0 instead of * and manually investigate tokio-console logs.

Additional context

No response

Would you like to work on fixing this bug?

no

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-consoleCrate: console.E-mediumEffort: medium.S-bugSeverity: bugS-featureSeverity: feature. This is adding a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions