You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What crate(s) in this repo are involved in the problem?
tokio-console
What is the issue?
First time using tokio-console, I did tokio-console 127.0.0.1:1234 and it kind of worked, not really. The display is blank, but when changing its size it displays something update reconnecting and t = tasks, r = resources, but doesn't seem to update anything.
Eventually I figured out that I'm supposed to do tokio-console http://127.0.0.1:1234 and that gives me the UI.
How can the bug be reproduced?
tokio-console 127.0.0.1:1234 (no http://)
Logs, error output, etc
No response
Versions
> tokio-console -V
tokio-console 0.1.7
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
no
The text was updated successfully, but these errors were encountered:
Tokio console can connect to a console subscriber over HTTP or
(on UNIX) via a socket. However, no check was performed to
ensure that the server string matched the HTTP(S) or FILE protocols.
This was reported to lead to strange behavior (#401).
This change adds an explicit check on the URI scheme to ensure that
it is one of `http`, `https`, or `file`.
closes: #401
Signed-off-by: hi-rustin <[email protected]>
What crate(s) in this repo are involved in the problem?
tokio-console
What is the issue?
First time using
tokio-console
, I didtokio-console 127.0.0.1:1234
and it kind of worked, not really. The display is blank, but when changing its size it displays something update reconnecting andt = tasks, r = resources
, but doesn't seem to update anything.Eventually I figured out that I'm supposed to do
tokio-console http://127.0.0.1:1234
and that gives me the UI.How can the bug be reproduced?
tokio-console 127.0.0.1:1234
(nohttp://
)Logs, error output, etc
No response
Versions
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
no
The text was updated successfully, but these errors were encountered: