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
Caused by:
failed to determine the most recently modified file in /path/to/package
Caused by:
failed to determine list of files in /path/to/package
Caused by:
File system loop found: /path/to/package/node/tools/node_modules/eslint/node_modules/eslint points to an ancestor /path/to/package/node/tools/node_modules/eslint
Why cargo before #10188 can succeed to build is that cargo ignores bad symlinks when checking it's mtime. Unfortunately #10188 proactively detects symlink loop and aborts when got one. I guess a revert might be fine.
…alexcrichton
Be resilient to most IO error and filesystem loop while walking dirs
Let `PathSource::walk` be resilient to most IO errors and filesystem loop.
This PR also
- Add a test validating the resilience against filesystem loop to prevent regression.
- Emit warning when filesystem loop found while walking the filesystem. This is the only way I can think of now to solve rust-lang#9528Fixesrust-lang#10213.
Problem
When running
cargo build
, an error is thrown:Steps
nodejs/node
to a package directorycargo build
Possible Solution(s)
No response
Notes
This does not occur on Cargo v1.56.0 (I'm experiencing this on 3787309).
Version
The text was updated successfully, but these errors were encountered: