| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| assert.throws(function() { | ||
| assert.throws(() => { | ||
| b.includes(() => {}); | ||
| }, /^TypeError: "val" argument must be string, number, Buffer or Uint8Array$/); |
There was a problem hiding this comment.
Can you put this regular expression in a variable so that it can be reused.
Sorry, something went wrong.
|
Please prefix the PR with test,buffer tag. Commit message guidelines |
Sorry, something went wrong.
Gotta mildly disagree with that. Just test: is fine. This is a change to the way a test works, not anything specific to buffer. The fact that it's a buffer test is incidental. No one looking for buffer changes is going to want to see this. And adding buffer just makes it harder to keep the first line to 50 chars. (EDIT: But if someone did put test,buffer: I wouldn't complain either. I just wouldn't insist that someone do that. And I would be especially careful with nits like that on first time contributors because they tend to internalize them as hard-and-fast rules.) |
Sorry, something went wrong.
|
test tag make sense to me for the reasons you outlined |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM if CI is green.
Sorry, something went wrong.
Sorry, something went wrong.
|
Looks like there was an issue with the build server, it started returning http 502, now that its back the above build has disappeared, it's returning http 404. Does CI need to be kicked-off again? |
Sorry, something went wrong.
Sorry, something went wrong.
|
@Trott haha. It was supposed to be test or buffer. I wasn't sure what was appropriate for this case. Anyway test it is 😄 |
Sorry, something went wrong.
|
CI failures on freebsd are unrelated |
Sorry, something went wrong.
Sorry, something went wrong.
* verify error message * use arrow funcs PR-URL: #11203 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
This commit is breaking tests in v7.x, maybe because of some semver-major... any plan to backport this? |
Sorry, something went wrong.
* verify error message * use arrow funcs PR-URL: nodejs#11203 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Should this be backported to v6.x-staging? If yes please follow the guide and raise a backport PR, if no let me know or add the dont-land-on label. |
Sorry, something went wrong.
* verify error message * use arrow funcs PR-URL: nodejs/node#11203 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Verify specific errors thrown by buffer.includes and change tests to use arrow functions as per latest testing guide.
Checklist
Affected core subsystem(s)
tests, buffer