| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The original commit was landed without running CITGM. Unfortunately this change breaks the module `d` which has over 500k downloads a day. It is worth mentioning that the compatibility hack can be removed without breaking anything. We should definitely revisit for the next Semver-Major but shipping this today will cause non trivial ecosystem breakages. Refs: nodejs#3384
Sorry, something went wrong.
|
can you post the citgm failure here please? |
Sorry, something went wrong.
|
here is an example of one of the failures module.js:520
throw err;
^
Error: Cannot find module 'd/lazy'
at Function.Module._resolveFilename (module.js:518:15)
at Function.Module._load (module.js:448:25)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/memoizee/lib/methods.js:6:21)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/memoizee/methods.js:3:18)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/cli-color/bare.js:10:22)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/cli-color/index.js:5:42)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/tad/lib/console.js:13:17)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/tad/index.js:8:20)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Module.require (module.js:561:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Users/mborins/code/d/node_modules/tad/bin/tad:22:13)
at Module._compile (module.js:617:30)
at Object.Module._extensions..js (module.js:628:10)
at Module.load (module.js:536:32)
at tryModuleLoad (module.js:479:12)
at Function.Module._load (module.js:471:3)
at Function.Module.runMain (module.js:658:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:613:3
npm ERR! Test failed. See above for more details.
|
Sorry, something went wrong.
|
thanks. I'm surprised we don't test this use of require. It is common to do that with lodash. |
Sorry, something went wrong.
|
@targos it seems like this commit specifically broke the case of requiring specific files in modules that only have a single character as a name. This will thankfully be limited to 26 cases! Hopefully this hint can help us with maybe landing this in the future |
Sorry, something went wrong.
|
CI failed completely on windows. Trying again https://ci.nodejs.org/job/node-test-commit-windows-fanned/13041/ |
Sorry, something went wrong.
|
@MylesBorins ...
A regression test for specifically this case would be helpful as a separate PR |
Sorry, something went wrong.
|
I don't think my implementation has the regression. I can import lazy from "d/lazy" at least. Ah, nervermind. When forcing it on (was some semver -rc detection wonkiness) I get errors too 😢 Error [ERR_MISSING_MODULE]: Cannot find module d/lazy |
Sorry, something went wrong.
|
Trying CI on Windows again now that #16639 is landed: https://ci.nodejs.org/job/node-test-commit-windows-fanned/13045/ ... that failed, but I may have restarted it wrong... trying again https://ci.nodejs.org/job/node-test-pull-request/11117/ |
Sorry, something went wrong.
|
got past the compile error on windows... should be good but letting the CI finish |
Sorry, something went wrong.
|
single windows failures parallel/test-async-wrap-uncaughtexception edit: make that two sequential/test-inspector-async-call-stack |
Sorry, something went wrong.
|
Both of which appear to be flaky |
Sorry, something went wrong.
|
Just waiting on AIX and OSX to finish... then will get this landed |
Sorry, something went wrong.
The original commit was landed without running CITGM. Unfortunately this change breaks the module `d` which has over 500k downloads a day. It is worth mentioning that the compatibility hack can be removed without breaking anything. We should definitely revisit for the next Semver-Major but shipping this today will cause non trivial ecosystem breakages. Refs: #3384 PR-URL: #16634 Refs: #3384 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
The original commit was landed without running CITGM. Unfortunately this change breaks the module `d` which has over 500k downloads a day. It is worth mentioning that the compatibility hack can be removed without breaking anything. We should definitely revisit for the next Semver-Major but shipping this today will cause non trivial ecosystem breakages. Refs: #3384 PR-URL: #16634 Refs: #3384 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| request.charCodeAt(0) !== 46/*.*/ || | ||
| (request.charCodeAt(1) !== 46/*.*/ && | ||
| request.charCodeAt(1) !== 47/*/*/)) { | ||
| var paths = modulePaths; |
There was a problem hiding this comment.
The use of charCodeAt jazz really complicates the logic. It was introduced in a pass to optimize lots of things but I suspect it was micro-opts carried a bit too far. Anyways, would this do to fix it:
if (! (request.length === 1 &&
request.charCodeAt(0) === codeOfDot) &&
! (request.charCodeAt(0) === codeOfDot &&
(request.charCodeAt(1) === codeOfDot ||
request.charCodeAt(1) === codeOfSlash))) {
Sorry, something went wrong.
|
@jdalton do you want to take a pass at a fix + test in a new PR?
|
Sorry, something went wrong.
|
Thanks @MylesBorins! I'm a bit time crunched at the moment but I'd dig picking it up at the end of the week if it's still available. I'll update my comment with findings from my local implementation today. |
Sorry, something went wrong.
The original commit was landed without running CITGM. Unfortunately this change breaks the module `d` which has over 500k downloads a day. It is worth mentioning that the compatibility hack can be removed without breaking anything. We should definitely revisit for the next Semver-Major but shipping this today will cause non trivial ecosystem breakages. Refs: nodejs/node#3384 PR-URL: nodejs/node#16634 Refs: nodejs/node#3384 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
The original commit was landed without running CITGM. Unfortunately this change breaks the module `d` which has over 500k downloads a day. It is worth mentioning that the compatibility hack can be removed without breaking anything. We should definitely revisit for the next Semver-Major but shipping this today will cause non trivial ecosystem breakages. Refs: nodejs/node#3384 PR-URL: nodejs/node#16634 Refs: nodejs/node#3384 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
The original commit was landed without running CITGM. Unfortunately this change breaks the module `d` which has over 500k downloads a day. It is worth mentioning that the compatibility hack can be removed without breaking anything. We should definitely revisit for the next Semver-Major but shipping this today will cause non trivial ecosystem breakages. Refs: nodejs/node#3384 PR-URL: nodejs/node#16634 Refs: nodejs/node#3384 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| Back | FazBrowse Home | New Git URL |
The original commit was landed without running CITGM. Unfortunately
this change breaks the module d which has over 500k downloads a day.
It is worth mentioning that the compatibility hack can be removed
without breaking anything.
We should definitely revisit for the next Semver-Major but shipping
this today will cause non trivial ecosystem breakages.
Refs: #3384