-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
fix: dont patch getuid
and getgid
on process anymore #809
#847
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just need to restore the uid
property.
Would you be open to also replacing getgid
in this PR too, since that change is pretty much the same thing?
it('.getuid() and .getgid()', () => { | ||
expect(typeof proc.getuid()).toBe('number'); | ||
expect(typeof proc.getgid()).toBe('number'); | ||
expect(typeof proc.getuid?.() ?? 0).toBe('number'); | ||
expect(typeof proc.getgid?.() ?? 0).toBe('number'); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we should remove this test entirely as it's not really covering anything useful now
process.getuid
under Windows #809getuid
and getgid
on process anymore #809
## [3.4.7](v3.4.6...v3.4.7) (2022-06-24) ### Bug Fixes * dont patch `getuid` and `getgid` on `process` anymore ([#847](#847)) ([1c19e87](1c19e87))
🎉 This PR is included in version 3.4.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Resolves #809