-
Notifications
You must be signed in to change notification settings - Fork 22
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
Intermittently Errno::ENOENT errors #98
Comments
Hi Brian! It looks like the Errno::ENOENT error you are getting is indicating a file does not exist even though you can see it in your directory. This also seems weird since on line 78 we check that the file exists: Do you think there is something in the background that is moving or renaming files? |
Yes it is super weird. I can't think of anything that would move or rename files, and we don't see anything like this anywhere else in our error monitoring. Any tips on how we could troubleshoot it? |
Hi @f1sherman! I want to check in and see if you're still experiencing this issue. Recently, one of the folks on our team made some improvements to this repo, and those changes may or may not impact this issue. We haven't been able to reproduce this issue, but we'll continue to keep an eye out for it. |
@ashleywillard thanks for the heads up! I haven't seen this crop up in at least 2 weeks. I'll try removing our code that swallows the error and report back here if it comes back. Thank you! |
@ashleywillard unfortunately this error came back after I removed our patch :(. |
Darn! We still have yet to see this error but I will let you know if we do. It seems like this issue might be tricky to reproduce on our end. |
We intermittently (a few times a week) see
Errno::ENOENT
errors when callingCodeOwnership.for_file
where code ownership claims that a file we're looking up ownership for doesn't exist. It happens for different paths, not always the same path. There doesn't seem to be any obvious pattern for when this happens. The file exists and is found on 99.9% of requests. I've included the gem-specific portion of the trace below. Any ideas on how to track this down? For now we've added abegin
/rescue
block around it, but obviously that's not an ideal solution. It's really weird given that I can pass a path that definitely doesn't exist toCodeOwnership.for_file
and it doesn't error, just returnsnil
.The error has the signature
Errno::ENOENT: No such file or directory @ rb_sysopen - path/to/file/that/exists.rb
.The text was updated successfully, but these errors were encountered: