| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
The way the test is written now makes it possible for future regressions to go undetected so that's no good, unfortunately. I'd simply call out to sysctl(1) with execSync() to check the value. There's at least one other instance of that in our test suite so it's not without precedent. |
Sorry, something went wrong.
|
Okay, I'll make these changes |
Sorry, something went wrong.
|
added these changes @bnoordhuis |
Sorry, something went wrong.
|
Can you try merging again? Had some lint errors, hopefully, they are fixed now. @bnoordhuis |
Sorry, something went wrong.
|
Can you please take a look? |
Sorry, something went wrong.
| const { execSync } = require('child_process'); | ||
|
|
||
| if (common.isLinux) { | ||
| const sysctlOutput = execSync('sysctl net.ipv4.ip_unprivileged_port_start').toString(); |
There was a problem hiding this comment.
Add a comment?
Sorry, something went wrong.
There was a problem hiding this comment.
Sure, should I add one now? (PR is closing to merging I think...)
Sorry, something went wrong.
There was a problem hiding this comment.
PR is closing to merging I think...
I am not sure what you mean here, you can still push changes and I'll re-run CI after :]
If you prefer to put it in another change to practice making changes in Node.js as a new contributor - that's also fine with me.
Sorry, something went wrong.
There was a problem hiding this comment.
I would like it if I could put it in another change so I can practice making changes, that would be really helpful!
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
fixes: #45838