| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
There are some RegExps with the same pattern which are left unchanged (lines 193, 198, 203 etc).
It seems the \b symbol after the ^ is unneeded.
Sorry, something went wrong.
There was a problem hiding this comment.
Unix data: "(function() { \"use strict\"; return 0755; })()\n
^^^^\n\nSyntaxError: Octal literals are not allowed in strict mode.\n\nnode via Unix socket> node via Unix socket> ", expecting /^SyntaxError: Octal literals are not allowed in strict mode/
assert.js:42
Sorry, something went wrong.
There was a problem hiding this comment.
Oh, sorry, I did not think this broke matching.
I think that removing the \b is safe only if we place ^ before)
Sorry, something went wrong.
There was a problem hiding this comment.
Ack and taken care of ^_^
Sorry, something went wrong.
There was a problem hiding this comment.
💯 on the wrapping!
Sorry, something went wrong.
There was a problem hiding this comment.
Nit: Now the whole thing would fit in a single line.
Sorry, something went wrong.
There was a problem hiding this comment.
@thefourtheye True! But doesn't it look cleaner this way ?
Sorry, something went wrong.
There was a problem hiding this comment.
I'm with @thefourtheye, also could drop the () => { } to get:
assert.throws(v8.Serializer, serializerTypeError);Now that's clean ✨
Sorry, something went wrong.
There was a problem hiding this comment.
Well two against one !! Ack and taken care
Sorry, something went wrong.
There was a problem hiding this comment.
Nit \b -> ^?
Sorry, something went wrong.
There was a problem hiding this comment.
(And below two instances too?)
Sorry, something went wrong.
There was a problem hiding this comment.
It seems this somehow breaks matching: #14607 (comment)
Sorry, something went wrong.
There was a problem hiding this comment.
Some error messages quote erroneous code before the error message itself, so for these messages, we can't use ^ anchor (or we should add the /m flag beside).
Sorry, something went wrong.
There was a problem hiding this comment.
OK, then \b it is!
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM if CI is green.
Sorry, something went wrong.
Sorry, something went wrong.
|
One aix fail in CI seems unrelated (parallel/test-async-wrap-getasyncid is crashed). |
Sorry, something went wrong.
Format commit wrapping lines containing RegEx and exceeding 80 chars. Fixes: nodejs#14586
Sorry, something went wrong.
|
CI failures seem unrelated. |
Sorry, something went wrong.
Format commit wrapping lines containing RegEx and exceeding 80 chars. PR-URL: nodejs#14607 Fixes: nodejs#14586 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
|
Landed in ad664ea |
Sorry, something went wrong.
Format commit wrapping lines containing RegEx and exceeding 80 chars. PR-URL: #14607 Fixes: #14586 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
|
This does not land cleanly in LTS. Please feel free to manually backport by following the guide. Please also feel free to replace do-not-land if it is being backported |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Format commit wrapping lines containing RegEx and exceeding 80
chars.
Fixes: #14586
Files Changed:
Checklist
Affected core subsystem(s)
test