Cargo check fails with internal error

[matklad]

The error looks like this:

λ cargo check --all --verbose
error: dep-info not in an understood format: /home/matklad/projects/fall/target/debug/.fingerprint/fall_gen-1d7df0cac95e3081/dep-bin-gen-1d7df0cac95e3081

Removing .target directory fixes the error. I don't think I understand what caused the error originally.

[alexcrichton]

Do you have the original source code I could poke around with? I wonder if something got corrupted by accident...

[matklad]

No, I originally expected that this was due to upgrade from 1.17.0 to 1.18.0, so I deleted target and tried compiling with 17 and then switching to 18, but everything worked fine then, and I was unable to reproduce the error at all :(

[mrcnski]

I just had the good luck to run into this. I was trying to build some changes I made to safe_authenticator.

❯ cargo test --verbose
error: dep-info not in an understood format: /Users/marcin/Dropbox/Work/maidsafe/safe_client_libs/target/debug/.fingerprint/safe_authenticator-151ddd9151afa849/dep-lib-safe_authenticator

The contents of the dep-lib-safe_authenticator file:

src/lib.rssrc/ffi/mod.rssrc/ffi/apps.rssrc/ffi/logging.rssrc/ffi/ipc.rssrc/access_container.rssrc/app_auth.rssrc/app_container.rssrc/config.rssrc/errors.rssrc/ipc.rssrc/revocation.rssrc/std_dirs.rssrc/test_utils.rs

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[stale]

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!