-
Notifications
You must be signed in to change notification settings - Fork 30k
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
test: Test process.setuid for bad argument types #19591
Comments
@dsinecos - go for it! |
dsinecos
added a commit
to dsinecos/node
that referenced
this issue
Mar 30, 2018
test process.setuid with an object as an argument. An equivalent test exists for process.seteuid Fixes: nodejs#19591
2 tasks
targos
pushed a commit
that referenced
this issue
Apr 4, 2018
Test process.setuid with an object as an argument. An equivalent test exists for process.seteuid. PR-URL: #19703 Fixes: #19591 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
BethGriggs
pushed a commit
that referenced
this issue
Dec 4, 2018
Test process.setuid with an object as an argument. An equivalent test exists for process.seteuid. PR-URL: #19703 Fixes: #19591 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While reading through the tests I found that there is a test for bad argument types for process.seteuid but there isn't a corresponding test (
process.setuid({})
) for bad argument types for process.setuidI think that a corresponding test could be added in the file to test bad argument types for process.setuid as well.
If this makes sense, I'd like to contribute through a PR on this.
The text was updated successfully, but these errors were encountered: