-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rename FilenameTooLong
to InvalidFilename
and also use it for Windows' ERROR_INVALID_NAME
#90955
Rename FilenameTooLong
to InvalidFilename
and also use it for Windows' ERROR_INVALID_NAME
#90955
Conversation
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
Seems reasonable to me. Since the ErrorKind mapping is something we keep stable, let's quickly get some more eyes on it before merging it: @rfcbot merge |
This comment has been minimized.
This comment has been minimized.
Team member @m-ou-se has proposed to merge this. The next step is review by the rest of the tagged team members: Concerns:
Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
One issue I've found while testing symlinks is that a symlink to an invalid file name can return So now I'm uncertain whether |
@rfcbot concern broken symlinks See #90955 (comment) |
Might it make sense to change |
Sounds good, I'm happy to switch to it if y'all agree with the nightly change. |
@rfcbot concern should-map-to-FilenameInvalid-renamed-from-FilenameTooLong |
Yes, I think this is the best idea. |
@JohnTitor Could you please update the PR to do that? (Let us know if you don't have the bandwidth to do so.) |
5bf5ce9
to
1bc408d
Compare
Sure! Updated as suggested in #90955 (comment). |
@rfcbot resolved should-map-to-FilenameInvalid-renamed-from-FilenameTooLong |
@m-ou-se I think this change should resolve your concern as well. |
ERROR_INVALID_NAME
as InvalidInput
FilenameTooLong
to FilenameInvalid
and also use it for Windows' ERROR_INVALID_NAME
@rfcbot resolve broken symlinks |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
FilenameTooLong
to FilenameInvalid
and also use it for Windows' ERROR_INVALID_NAME
FilenameTooLong
to InvalidFilename
and also use it for Windows' ERROR_INVALID_NAME
This comment has been minimized.
This comment has been minimized.
cb8778c
to
06f416b
Compare
Co-authored-by: Mara Bos <m-ou.se@m-ou.se>
This comment has been minimized.
This comment has been minimized.
06f416b
to
a898b31
Compare
@bors r+ |
@m-ou-se: 🔑 Insufficient privileges: Not in reviewers |
Uh. @rust-lang/infra ^ |
@bors r+ |
📌 Commit a898b31 has been approved by |
…nput, r=m-ou-se Rename `FilenameTooLong` to `InvalidFilename` and also use it for Windows' `ERROR_INVALID_NAME` Address rust-lang#90940 (comment) `ERROR_INVALID_NAME` (i.e. "The filename, directory name, or volume label syntax is incorrect") happens if we pass an invalid filename, directory name, or label syntax, so mapping as `InvalidInput` is reasonable to me.
…nput, r=m-ou-se Rename `FilenameTooLong` to `InvalidFilename` and also use it for Windows' `ERROR_INVALID_NAME` Address rust-lang#90940 (comment) `ERROR_INVALID_NAME` (i.e. "The filename, directory name, or volume label syntax is incorrect") happens if we pass an invalid filename, directory name, or label syntax, so mapping as `InvalidInput` is reasonable to me.
…askrgr Rollup of 10 pull requests Successful merges: - rust-lang#90955 (Rename `FilenameTooLong` to `InvalidFilename` and also use it for Windows' `ERROR_INVALID_NAME`) - rust-lang#91607 (Make `span_extend_to_prev_str()` more robust) - rust-lang#92895 (Remove some unused functionality) - rust-lang#93635 (Add missing platform-specific information on current_dir and set_current_dir) - rust-lang#93660 (rustdoc-json: Add some tests for typealias item) - rust-lang#93782 (Split `pauth` target feature) - rust-lang#93868 (Fix incorrect register conflict detection in asm!) - rust-lang#93888 (Implement `AsFd` for `&T` and `&mut T`.) - rust-lang#93909 (Fix typo: explicitely -> explicitly) - rust-lang#93910 (fix mention of moved function in `rustc_hir` docs) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Address #90940 (comment)
ERROR_INVALID_NAME
(i.e. "The filename, directory name, or volume label syntax is incorrect") happens if we pass an invalid filename, directory name, or label syntax, so mapping asInvalidInput
is reasonable to me.