-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Crash with UTF8 error (similar to Issue #9), fatal error when trying to run in cargo #23
Comments
Hmm, I can look at this later tonight but can you run the unit tests to see if they break on your machine? What version of steamcmd are you using? Also, try deleting 2> won't work since I removed the logging. I think I can hide it under a feature flag, so I might put it back in, and get you to run again. Thanks! |
This may sound stupid, but how do I run the unit tests? dpkg reports the version to be "Version: 0~20180105-4" when freshly installed, but steamcmd autoupdates when it launches |
`cargo test`
Rust is a pretty fun language to learn !
…On Fri, May 28, 2021, 15:40 Patrick ***@***.***> wrote:
This may sound stupid, but how do I run the unit tests?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUQSOVHYW5RQALKBDPOAH3TP7WTTANCNFSM45XHHB6A>
.
|
These are the results of the unit-test.txt from what I can tell, it passed the tests |
Yeah unit tests are working. Are there any special characters in your steam username? Maybe windows line endings? What happened when you tried to delete the cache? Same problem? Trying to think what it could be |
I think what may have happened is that you had an old version of the code, it crashed, and it got your config in a strange state. |
Success! No errors, no weirdness now! I also ran I will now close this issue, thanks for fixing! |
Similar to Issue #9, steam-tui puts up a fatal error when starting it normally:
Problem("Utf8Error { valid_up_to: 4502, error_len: Some(1) }")
However, when trying to run it with
cargo run 2> err
, I get another error:Problem("Unknown command sent [0mUsage:\n\tlogin <username> [<password>] [<Steam guard code>]\n")
err.txt
So I tried to build it again (using
cargo build --release
) and this happenedI am using Ubuntu 21.04 over a SSH connection
Edit: I just tested this in the VM's console (no SSH involved this way) and while it didn't do stuff like in that picture, it still failed like above
The text was updated successfully, but these errors were encountered: