This repository was archived by the owner on Aug 31, 2023. It is now read-only.
This repository was archived by the owner on Aug 31, 2023. It is now read-only.
🐛 Infinite symlink expansion error when there's no infinite symlink AFAICT #4193
Description
Environment information
CLI:
Version: 11.0.0
Color support: true
Platform:
CPU Architecture: x86_64
OS: linux
Environment:
ROME_LOG_DIR: unset
NO_COLOR: unset
TERM: "xterm-256color"
Rome Configuration:
Status: loaded
Formatter disabled: false
Linter disabled: false
Workspace:
Open Documents: 0
Discovering running Rome servers...
What happened?
- running
npx rome check . - It complains about a bunch of file symlinks I have
For example:
../tools/node/npm-runner.js internalError/fs ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Infinite symlink expansion
✖ Rome encountered a file system entry that leads to an infinite symbolic link expansion, causing an infinite cycle: ../tools/node/npm-runner.js
Problems:
- I have no idea what working directory it's in because I run rome from
.and the npm-runner.js script is located atworkflow/tools/node/npm-runner.js - I have no idea what the source of the symlink is that it's having problems with
- npm-runner.js is not a symlink:
$ ls -l workflow/tools/node/npm-runner.js
-rwxr-xr-x 1 vlovich vlovich 7707 Jan 24 18:20 workflow/tools/node/npm-runner.js
Relevant information:
An example of a symlink looks like:
ls -l scripts/my-tool
lrwxrwxrwx 1 vlovich vlovich 36 Jan 12 20:22 scripts/my-tool -> ../workflow/tools/node/npm-runner.js
workflow is a submodule to another project. I get the similar errors when running rome from within the submodule (or even as a standalone checkout) so most of the errors about the symlinks that exist within workflow (the npm-runner.js script is reused within workflow and within projects that import it).
Expected result
Simple symlinks to JS files shouldn't cause infinite symlink errors.
Code of Conduct
- I agree to follow Rome's Code of Conduct