| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
/cc @nodejs/platform-macos |
Sorry, something went wrong.
|
@chris--young thank you very much for the contribution 🥇 It would be extra beneficial if you tried to add some test cases that validate that the filename is indeed passed to the callback. That way we could run automated testing that validate the doc. |
Sorry, something went wrong.
|
AIX too please. bash-4.3$ uname AIX bash-4.3$ cat w.js var fs = require('fs');
fs.watch('myfile', (eventType, filename) => {
console.log(`event type is: ${eventType}`);
if (filename) {
console.log(`filename provided: ${filename}`);
} else {
console.log('filename not provided');
}
});bash-4.3$ node w.js & [1] 1769476 bash-4.3$ echo hello > myfile bash-4.3$ event type is: change filename provided: myfile event type is: change filename provided: myfile |
Sorry, something went wrong.
There was a problem hiding this comment.
Per my comment - will you please add AIX also into the list?
Sorry, something went wrong.
There was a problem hiding this comment.
I would add Windows too. You can also add AIX according to @gireeshpunathil's suggestion.
Sorry, something went wrong.
There was a problem hiding this comment.
I just checked, it passes on windows.
Sorry, something went wrong.
There was a problem hiding this comment.
A few nits
Sorry, something went wrong.
There was a problem hiding this comment.
I just checked, it passes on windows.
Sorry, something went wrong.
There was a problem hiding this comment.
If you could use assert.ifError if (err) assert.fail(err); instead. It will rethrow the error so we know what went wrong.
assert(!err) will just say true != false
Sorry, something went wrong.
There was a problem hiding this comment.
For the test to pass on Windows you should remove the common.refreshTmpDir();. Don't worry about it, the test harness will take care of it.
Sorry, something went wrong.
There was a problem hiding this comment.
you can replace the whole callback with (err) => assert.ifError(err)
Ref: #13092 (comment)
Sorry, something went wrong.
There was a problem hiding this comment.
you should replace the whole callback with common.mustCall((err) => {if (err) assert.fail(err)})
Ref: #13115
Sorry, something went wrong.
Sorry, something went wrong.
|
Any idea what's up with that failed windows-fanned test? Seeing this in the logs... node-test-binary-windows » 1,vs2015-x86,win2008r2 completed with result FAILURE I don't have a Windows box to test on right now, should be able to setup a vm over the weekend if needed. |
Sorry, something went wrong.
Ignore, it's a infrastructure fail. Also the linux fan is backlogged. |
Sorry, something went wrong.
|
@chris--young if you're not aware of our landing procedure; now that your part is done, we keep the PR open for 48-72 hours so that anyone who might want to voice an opinion will have a chance. Thanks again! |
Sorry, something went wrong.
|
sweet |
Sorry, something went wrong.
There was a problem hiding this comment.
Nit: can you please replace this with assert.ifError()?
Edit: Just read @refack comments against assert.ifError(). It is actually widely used in our tests but what is used here is also ok so feel free to ignore this.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
@chris--young - thanks! I am fine with the changes.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for your contribution! Can you please change the message of the first commit to use doc:, not docs:? That can be fixed by whoever lands the commit as well, though.
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-commit/10067/ |
Sorry, something went wrong.
There was a problem hiding this comment.
I'd prefer it to be either a one-liner or to have braces, but maybe it's just me, and it clearly does not violate the code style this way too, so you can ignore this comment :)
Sorry, something went wrong.
There was a problem hiding this comment.
I really think we should use assert.ifError(err) in these cases.
Sorry, something went wrong.
There was a problem hiding this comment.
+1
Either one liner or braces.
Sorry, something went wrong.
There was a problem hiding this comment.
Ditto
Sorry, something went wrong.
|
@chris--young we raised a code style nit, then this will land. |
Sorry, something went wrong.
|
@refack made those changes. It looks like a new test is failing now, possibly another infrastructure fail Checking out Revision 21535c38a3f800117089872f890e9d1f336024e0 (refs/remotes/origin/_jenkins_local_branch) > git config core.sparsecheckout # timeout=10 > git checkout -f 21535c38a3f800117089872f890e9d1f336024e0 FATAL: Could not checkout 21535c38a3f800117089872f890e9d1f336024e0 hudson.plugins.git.GitException: Command "git checkout -f 21535c38a3f800117089872f890e9d1f336024e0" returned status code 128: stdout: stderr: fatal: reference is not a tree: 21535c38a3f800117089872f890e9d1f336024e0 |
Sorry, something went wrong.
|
Ignore it fedora22 is obsolete anyway. I'm landing this. |
Sorry, something went wrong.
also added regression tests PR-URL: nodejs#13111 Fixes: nodejs#13108 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Alexey Orlenko <eaglexrlnk@gmail.com>
| Back | FazBrowse Home | New Git URL |
macOS is not currently listed as a supported os for the fs.watch filename argument, but it does work. This commit updates the documentation to reflect that.
Fixes: #13108
Checklist
Affected core subsystem(s)
docs, tests