-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
add paths to file error messages #38242
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
Conversation
fixes #38005 |
Also fixes #33236. |
Also #33201. |
476fe61
to
0891bc3
Compare
0891bc3
to
3fe5ea7
Compare
c37c664
to
c2603b1
Compare
c2603b1
to
fc7b55b
Compare
The FreeBSD failure seems unrelated, and the MacOS failure is on the "clean it out" stage: I suspect this could have been caused by the permissions changes in the builds for #38235. |
Okay, this is ready to go. |
Bump! A few minutes ago I wished this was already merged 😄 |
Seems like a huge improvement to me! I'm assuming that since these are all I/O operations none of them are performance sensitive enough that having error paths capture variables matters. |
Makes the error messages for various file operations more descriptive, including the paths and other arguments.
EDIT: closes #38005, closes #33236, closes #33201.