-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v5.0.0-proposal #3920
v5.0.0-proposal #3920
Conversation
Overall package sizeSelf size: 5.82 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## v5.x #3920 +/- ##
==========================================
+ Coverage 84.70% 85.01% +0.30%
==========================================
Files 237 238 +1
Lines 10147 10176 +29
Branches 33 33
==========================================
+ Hits 8595 8651 +56
+ Misses 1552 1525 -27 ☔ View full report in Codecov by Sentry. |
BenchmarksBenchmark execution time: 2024-01-09 18:18:33 Comparing candidate commit 183ed9d in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 259 metrics, 6 unstable metrics. scenario:plugin-graphql-with-depth-on-max-18
|
* Update typing for `tracer.trace` If options are not specified (and therefore if `options.orphanable !== false`) then `span` and the `done` callback are guaranteed to be set * Fix other TypeScript errors * Make trace done callback return value void --------- Co-authored-by: Janek Lasocki-Biczysko <janek.lb@gmail.com>
* drop support for node 16 in preparation for v5 release
* Ignore samples without endpoints instead of asserting all will have endpoints * Emit base64-encoded pprof in an error message so we can debug flaky tests
* Add CPU profiler * Avoid restarting profiling for last collect Upon process exit, profiler collects profiles a last time and was restarting all profilers before stopping them. Avoid this useless restart by changing the profiler API and make `profile()` methode take a restart argument. * Bump pprof-nodejs version
72a6d9d
to
b4cc214
Compare
@@ -0,0 +1,130 @@ | |||
'use strict' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm, is this feature not landing in the v4.x branch? @Qard @khanayan123
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a minor. It should have already have landed, as far as I know. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this feature already landed on v4.x and v3.x. This PR rebased on top of master but v5.x is behind master which is why this commit is showing up
b4cc214
to
183ed9d
Compare
aren't we missing updates in the README ? like saying that v5 is latest instead of v4 and updating the release schedule table ? |
Those updates are in this PR: #3918 which will be merged in after this PR |
Breaking Changes
More information about the breaking changes from this release can be found in
the migration guide.
Features
Improvements