-
Notifications
You must be signed in to change notification settings - Fork 386
Error when there is an unsupported flag for opening a file #987
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
☔ The latest upstream changes (presumably #983) made this pull request unmergeable. Please resolve the merge conflicts. |
a5dbdee
to
a1c6797
Compare
400ca87
to
d73fae1
Compare
Hm... now the odd part is that CI works here, isn't it? When you do |
(Also #973 still has some unresolved comments, not sure if you wanted to do separate PRs or add them here.) |
Hmm yeah, that's odd. Maybe it happens because some of the Quote from man:
So it is ok to just return EDIT: Should I just remove the |
49fc9c8
to
f76f8ce
Compare
I think I won't be adding more changes to this PR. I'll take care of those comments after the changes to make public the |
8b032f5
to
2487223
Compare
📌 Commit 2487223 has been approved by |
…lfJung Error when there is an unsupported flag for opening a file @RalfJung this is my attempt to check for undesired flags. I also changed fcntl to error when doing any other action besides getting the flags for a fd
☀️ Test successful - checks-travis, status-appveyor |
@RalfJung this is my attempt to check for undesired flags. I also changed fcntl to error when doing any other action besides getting the flags for a fd