-
Notifications
You must be signed in to change notification settings - Fork 140
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
Use crate isatty to resolve Windows build errors #14
Conversation
Error was due to lack of 'isatty()' method and failing to resolve enums in scope. Removed semver and toml as they were unused. Remove isatty() function infavor of isatty::stdout_isatty() Swap cfg(unix) to cfg(not(windows)) Regenerate Cargo.lock to resolve older Hyper-Tls security vulnerability. Cargo format ran over the project after change were made.
I'd feel a lot better about a Windows patch if there were Windows CI. Would it help if I set up something like Appveyor we could test it with? |
I have built and used this locally on my Windows 10 machine personally. That said I'm not a fan of 'works on my machine' so I understand wanting to run it through an official test. I don't have any experience setting up a windows CI w/ Appveyor but have seen a few examples with a quick search. If there are any changes/additions you need me to make please let me know. |
Will look at setting up Appveyor this weekend. Sorry for the delay. |
Okay, took a bit longer than I said but I've set up Appveyor and it appears to be reproducing your reported problem: https://ci.appveyor.com/project/tarcieri/cargo-audit/build/1.0.4/job/5ssqqoyg096brd9w Can you rebase and see if it builds successfully now? |
Error was due to lack of 'isatty()' method and failing to resolve enums in scope. Removed semver and toml as they were unused. Remove isatty() function infavor of isatty::stdout_isatty() Swap cfg(unix) to cfg(not(windows)) Regenerate Cargo.lock to resolve older Hyper-Tls security vulnerability. Cargo format ran over the project after change were made.
Build is failing due to older Rust version on the windows machine. Related Issues:
It's mentioned that rust 1.17.0 was when this was stabilized. https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1170-2017-04-27 |
Appveyor: Take 2
Okay, try rebasing on master again. I tried a different Appveyor config which appears to successfully be pulling in Rust 1.20 stable using rustup: #16 |
Error was due to lack of 'isatty()' method and failing to resolve enums in scope. Removed semver and toml as they were unused. Remove isatty() function infavor of isatty::stdout_isatty() Swap cfg(unix) to cfg(not(windows)) Regenerate Cargo.lock to resolve older Hyper-Tls security vulnerability. Cargo format ran over the project after change were made.
It's green! 🎉 Anything else you want to do before I merge? (e.g. squash) Otherwise I'm fine to merge as-is |
If you can't squash on merge then let me know and I can look into doing it on my side. Just re-formatted it with the latest rustfmt-nightly. Otherwise I'm fine with merging as-is. |
Released as v0.2.1 |
Factor integration tests into the tests/ directory
metadata: Generalize into `Key` and `Value` types
README.md: Header quoting fixup
Bump once_cell from 1.2.0 to 1.3.1
Error was lack of
isatty()
method and failing to resolve enums in scope (full error message at bottom):isatty()
functions in favor of usingisatty::stdout_isatty()
get_term()
Security Vulnerability:
Not essential to fix:
cfg(unix)
tocfg(not(windows))
.Full build error: