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
Rubocop fails with File name too long when finding target files #9593
Comments
Oho, I've managed to reproduce this, full steps below:
It seems the presence of a directory entry called Why I had that directory entry, I don't know - probably something I fat fingered at some point. Wether or not this is a bug in Rubocop, I'll let someone else be the judge of. Was I surprised by this behavior; very much so. Do you want me to merge these extra details into the main issue description? |
…`{}` Fixes rubocop#9593. This PR fixes the following error when processing a directory is named `{}`. ```console % mkdir {} % rubocop (snip) File name too long - /tmp//////////////////////////////////////////////... ```
Thank you for the feedback and investigation. That extra details comment does not have to be merged. I have reproduced this issue and opened #9594. |
In one of our projects, we've started seeing the following error when running Rubocop:
The error is followed by a huge stacktrace that seems to indicate some kind of recursion not stopping correctly, see full output below.
Steps to reproduce
Unfortunately I cannot provide a reproducible project (closed source, proprietary etc etc), but all I have to do to reproduce the problem is run:
Expected behavior
I would expect Rubocop to output a list of the files it's about to process. Curiously, it is only this folder that seems to result in that behavior. If I
cd app
fx and rerunrubocop --force-default-config --list-target-files
it works as expected.Actual behavior
RuboCop version
The text was updated successfully, but these errors were encountered: