| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
It should resolve the regressions while we work on fixing them. Refs: nodejs#54521
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## main #54565 +/- ##
==========================================
- Coverage 87.33% 87.33% -0.01%
==========================================
Files 649 649
Lines 182626 182620 -6
Branches 35041 35040 -1
==========================================
- Hits 159503 159489 -14
- Misses 16394 16404 +10
+ Partials 6729 6727 -2
|
Sorry, something went wrong.
|
If this is accepted, it should be fast-tracked for inclusion in #54560 |
Sorry, something went wrong.
|
Fast-track has been requested by @targos. Please 👍 to approve. |
Sorry, something went wrong.
|
@bricss please do not approve fast-track requests :] (or you know, start making PRs and join as a collaborator that also works :)) |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
@targos can you fix commit msg (PR-URL)? |
Sorry, something went wrong.
| "utf8WriteStatic", | ||
| SlowWriteString<UTF8>, | ||
| &fast_write_string); | ||
| SetMethod(context, target, "asciiWriteStatic", SlowWriteString<ASCII>); |
There was a problem hiding this comment.
non-blocking nit: perhaps consider adding a TODO comment?
Sorry, something went wrong.
|
@ronag I don't see a problem in the commit message. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
Sorry, something went wrong.
|
This message appears (to collaborators) on all the pull requests of the project. Unfortunately there is no way to customize it but the goal is to prevent merging by accident using the GitHub UI. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
It should resolve the regressions while we work on fixing them. Refs: #54521 PR-URL: #54565 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
Now that Node.js 22.8 is available with a workaround (nodejs/node#54565) for the bug in 22.7 that caused 'RangeError: "length" is outside of buffer bounds' errors in exporter tests (see open-telemetry#4953), we can unpin the Node.js v22 used for unit tests. This undoes the pinning from open-telemetry#4957.
| Back | FazBrowse Home | New Git URL |
It should resolve the regressions while we work on fixing them.
Refs: #54521