| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
It's probably not the best way to fix the issue. /cc @mscdex |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Could you add:
assert.strictEqual(path.win32.normalize('bar\\foo..\\..\\'), 'bar\\');
assert.strictEqual(path.win32.normalize('bar\\foo..\\..\\baz'), 'bar\\baz');
assert.strictEqual(path.win32.normalize('bar\\foo..\\'), 'bar\\foo..');Or alternatively find the coverage
Sorry, something went wrong.
There was a problem hiding this comment.
done
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
We could probably refactor this whole thing for TF&I anyway
Sorry, something went wrong.
Good luck. |
Sorry, something went wrong.
|
This needs a rebase |
Sorry, something went wrong.
|
Looks like I forgot about this PR... Done. |
Sorry, something went wrong.
|
CI failed on arm, trying again https://ci.nodejs.org/job/node-test-commit-arm/11784/ |
Sorry, something went wrong.
PR-URL: nodejs#14107 Fixes: nodejs#14105 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs/node#14107 Fixes: nodejs/node#14105 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs/node#14107 Fixes: nodejs/node#14105 Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#14107 Fixes: nodejs#14105 Reviewed-By: Refael Ackermann <refack@gmail.com>
|
I've backported to v6.x Please let me know if it should be backed out |
Sorry, something went wrong.
|
I've landed this back on v6.x along with 19d2d6611c which fixed the security vulnerability. Please let me know if you think they should be backed out /cc @nodejs/security @nodejs/tsc |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes: #14105
Checklist
Affected core subsystem(s)
path