-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Dependencies are not sorted error on Windows #56
Comments
Hmm, is there any chance it could be a line-ending thing? I also noticed one of the files does not end with |
I'm guessing you can see the logs so here is the windows job with |
I think I know why it fails. When the repo is cloned on windows, the |
Wow, nice find! I'll look into finding a better cross-platform way to compare. I wonder if ignoring the difference would be ok, any thoughts? |
Maybe you could compare the parsed |
That may work, I'd have to look into it after switching to the actual |
I ran into probably the same issue. I have a Cargo.toml file like this: [package]
name = "foo"
description = "bar"
version = { workspace = true }
publish = { workspace = true }
edition = "2021"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[build-dependencies]
fs_extra = "1.3.0"
sysinfo = "0.28.2" On Linux, So I don't have EDIT: Yes, when I convert the file to CRLF and run |
@lynn Yep I am seeing the same thing When there are extra lines in the middle of the file, if it is in LF format, then the Windows version of cargo-sort will not remove them. Whereas the Linux version will. |
I was trying to setup CI for one one my repo including
cargo sort --check
, but the check fail on Windows while it succeeds on Linux. I don't have a Windows machine so I cannot test this outside of the Github actions.The repo is here. The logs of the failing job are here.
I don't know if you can see the logs, so here are the logs for ubuntu and windows.
I don't really know what more I can say, but if you need more input, I'll gladly answer.
The text was updated successfully, but these errors were encountered: