GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — tools: increase maximum line length to 120 characters by Trott · Pull Request #41586 · nodejs/node Conversation
targos
approved these changes
This was referenced
Member
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Mesteery
approved these changes
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
mcollina
approved these changes
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lgtm
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Member
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
jasnell
approved these changes
BethGriggs
approved these changes
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
bnb
approved these changes
|
There was an error while loading. Please reload this page.
Massively favor eliminating line breaks. In general, it seems that the ecosystem has adopted this as a standard, and it's extremely strange for us to be an outlier. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
On a side note, I suspect that most of the ecosystem doesn't need to backport documentation changes to multiple release lines with diverging commit histories, so they are probably less concerned about the increased number of conflicts and the reduced usefulness of git operations such as |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in 870044f |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #41586 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Tierney Cyren <[email protected]>
PR-URL: #41586 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Tierney Cyren <[email protected]>
PR-URL: #41586 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Tierney Cyren <[email protected]>
PR-URL: #41586 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Tierney Cyren <[email protected]>
PR-URL: #41586 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Mestery <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Tierney Cyren <[email protected]>
The previous deploy (1cf105f) failed its own postbuild verification on Vercel — correctly. On Linux, nf3 nests version-conflicted deps as symlinks *inside* store packages (google-auth-library/node_modules/gaxios and 21 friends), and fs.cpSync({ dereference: true }) only dereferences the top-level path: nested links are recreated as links (nodejs/node#41586), so the "materialized" tree still dangled. Windows never showed it because nf3's junction layout keeps every link top-level, which is exactly why the local verification passed while Vercel's failed. The copy is now hand-rolled: copyReal() stats through symlinks at every depth, so the output contains none regardless of layout. Verified in a clean node:24 container from a tarball of this tree: npm ci + VERCEL=1 build exit 0, 19 links materialized, `find -type l` = 0, and the function artifact serves / at 200 and /api/available-models at 200 in the same container. Also makes the Sentry sourcemap upload non-fatal via errorHandler. The plugin's default is to throw and kill the build on any upload failure — a wrong org slug, an expired token, a Sentry outage. Observability must never take down a deploy. Exercised in the same container with deliberately invalid SENTRY_* values: three 401s from Sentry, three warnings in the log, build exit 0, and zero .map files left in the output. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.