-
Notifications
You must be signed in to change notification settings - Fork 158
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
filepath.Walk():bad file descriptor #56
Comments
Sorry, I cannot reproduce this as is. Can you provide more detail? What are the directory contents? Is this inside a container? A mounted FS? What's the OS? |
Same error on macOS BigSur 11.1. It works without error on docker (for mac). |
In my environment, adding |
I ran into this same issue (macOS Big Sur 11.2.1). I'm not sure exactly what the cause is, but I traced it down to a function called Happily, I discovered that this call hierarchy is only invoked when using the |
Good job tracing the issue back to the syscall level. Without specifics it is hard to reason about what is going wrong but
Thanks for the suggestion, there is already a section in the README about Mac OS X + polling. Is there something missing? |
Lol, that was my thinking as well. "Whatever that means".
I wish I could be of more help but I wasn't able to figure anything out in this regard. I did try i.e. --exclude-dir=".git", as well as some other dirs, however none of them solved the issue. I didn't go through that approach with much rigor, though, and doing so could lead to further evidence (i.e. excluding all directories in my repo and then adding them back 1 by 1 until I trigger the bug). I wish I could point you to the repo that this came up for me in so that you could investigate further (assuming you have access to a macOS system) however its been made private by the company I work for (obligatory check us out at https://goteleport.com!). No promises about the timeline, but I will add this to my running todo list to do it myself. Alternately or in concert, perhaps @wyatt-troia or @ypresto have an open source repo to point you at that you can use to repro.
Ah, indeed there is. Nope no suggestions, I just need to read the README more carefully next time. |
I understand :) Just a quick check: there were no special files like FIFOs, symlinks or unusually big files involved and no special file systems (like for example, running inside a container or a VM)? |
There are no FIFOs and the largest individual file is 32K. One directory has symlinks but excluding it does not fix the bug. Update:I have an update for you, having just spent some time this morning investigating this. The approach I took initially was -- for each directory in the repo, navigate into that directory and run a This was fruitful in that I identified several directories As a sanity check I next ran the I took all of the files and directories out of the repo, and then began adding them back in 1 by 1, running The interesting thing here is, if I navigate into As far as I can tell, there is nothing out of the ordinary about this directory. It is a perfectly normal directory of regular size with the same attributes as the other directories currently in the repo that aren't causing this issue:
At this point I'm thoroughly stumped, seeking suggestions of what I might try next. |
Thank you so much for the debugging effort, this is quality information! It might of course be that there is something special going on for that directory (or your file system/disk is broken :))
Thanks again for putting time and effort into this :) |
I successfully ran CompileDaemon a month ago when I downloaded it, but now whenever I try to run it I get:
I've tried deleting the src and bin files for CompileDaemon and running
go get "github.com/githubnemo/CompileDaemon"
, but it didn't change anything.I'm on a 2017 Macbook Pro.
The text was updated successfully, but these errors were encountered: