| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
I think you’re right, but it might be even simpler to change * to + in the regex (unless I’m missing something)?
Sorry, something went wrong.
|
I agree with @addaleax, either we allow passing foo= as a key that's equal an empty value, or we disallow it at which point it's better to match + directly. |
Sorry, something went wrong.
|
@addaleax, @benjamingr PTL, if I've understood you correctly) |
Sorry, something went wrong.
|
BTW, why [\s\S]? Do we have or allow \n in the CLI arguments? |
Sorry, something went wrong.
I would guess it does not actually matter. It might be nice for scripts to be able to set string parameters to whatever they want, including text containing newlines… ¯\_(ツ)_/¯ |
Sorry, something went wrong.
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Oops, I goofed and landed this without a CI run (it got batched in with a couple of other ones I was working on landing). Looks like the change breaks test/sequential/test-benchmark.http.js. Revert PR is in. |
Sorry, something went wrong.
|
@jasnell Sorry, I had to run the CI. Trying to understand how to fix. |
Sorry, something went wrong.
|
No worries, I should have double checked. I had it grouped in with a set of others that I was landing all together and missed it entirely. |
Sorry, something went wrong.
|
It seems we do have cases as key= as valid CLI params: Trying to grep another possible cases... |
Sorry, something went wrong.
|
Sorry, I have definitely made a sloppy unchecked assumption about key=: 20 morenode/benchmark/path/basename-posix.js Line 7 in eba2c62 node/benchmark/path/basename-win32.js Line 7 in eba2c62 node/benchmark/path/dirname-posix.js Line 7 in eba2c62 node/benchmark/path/dirname-win32.js Line 7 in eba2c62 node/benchmark/path/extname-posix.js Line 7 in eba2c62 https://github.com/nodejs/node/blob/eba2c62bb10fb65785050600212f70d38f1ffba3/benchmark/path/extname-win32.js node/benchmark/path/join-posix.js Line 7 in eba2c62 node/benchmark/path/join-win32.js Line 7 in eba2c62 node/benchmark/path/parse-posix.js Line 7 in eba2c62 node/benchmark/path/parse-win32.js Line 7 in eba2c62 node/benchmark/path/resolve-posix.js Line 7 in eba2c62 node/benchmark/path/resolve-win32.js Line 7 in eba2c62 node/benchmark/util/normalize-encoding.js Line 14 in 34bf31e |
Sorry, something went wrong.
Sorry, something went wrong.
|
CI fails only on Windows possibly with ref to #12475 Dear reviewers, could you re-review? |
Sorry, something went wrong.
Sorry, something went wrong.
|
Post mortem on the original botched landing: I believe that I simply had ended up putting this in the wrong list when I was organizing which PRs to land and which needed more work. This one obviously should have gone in the latter list. Since it was a change to benchmarks and we've only recently added benchmark tests to our CI set, I haven't got myself in the habit yet of running make test on benchmark: PRs. I ran make lint and went with it. Sorry all. |
Sorry, something went wrong.
|
@jasnell, @addaleax, @benjamingr, @joyeecheung, @jseijas — Does it still LGTY after the last change? |
Sorry, something went wrong.
There was a problem hiding this comment.
Yes, still LGTM :)
Sorry, something went wrong.
|
Still LGTM |
Sorry, something went wrong.
|
Still LGTM 👍 |
Sorry, something went wrong.
|
Still LGTM |
Sorry, something went wrong.
|
New CI to be sure: https://ci.nodejs.org/job/node-test-pull-request/7519/ |
Sorry, something went wrong.
|
Timeout in sequential/test-benchmark-child-process on Windows. Trying again: https://ci.nodejs.org/job/node-test-pull-request/7521/ UPD. Waiting for #12518 |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #12429 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Marking as dont-land as I think this depends on #7094, which was semver-major. Correct me if I'm wrong. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
benchmark
I can't think up any case when match is not null while match[1] is falsy here, as the first group does not use a quantifier that can end up in an empty string. So I suppose the match[2] is intended to prevent arguments like n=. However, I may miss something obvious.