| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Several provider ids have been removed that are no longer in use. Others have been updated to match their class constructors. Add test to ensure all internally listed providers are used.
If the constructor can't assign a class id then the heap snapshot will not be able to report the object. So ensure that all AsyncWrap instances use a FunctionTemplate instance with an internal field count >= 1.
To be clear, async wrap will still work during this time, correct? Otherwise one PR may be more appropriate? |
Sorry, something went wrong.
|
@Fishrock123 Each PR will have a small set of fixes. No PR will prevent AsyncWrap from working at least as well as it does today. This PR fixed outdated providers list and not all instances being reported in the heap snapshot. |
Sorry, something went wrong.
|
Sounds good to me then. I definitely can't actually review this haha. |
Sorry, something went wrong.
There was a problem hiding this comment.
These two will throw errors. Doesn't it make it major change? If this is an internal function, do we really need this?
Sorry, something went wrong.
There was a problem hiding this comment.
This doesn't throw an error. It aborts. The first couldn't have happened anyway because of how the function signature works. It's there as a sanity check for future development. The latter should never have been happening as it would have caused issues when iterating the heap.
Sorry, something went wrong.
|
Can you please summarize what this PR does and why it is necessary? Edit:
Ah I see. I'll try to find what providers are. |
Sorry, something went wrong.
There was a problem hiding this comment.
Mild cognitive dissonance here, the _t suffix makes it look like the variables are typedefs at a quick glance.
Sorry, something went wrong.
There was a problem hiding this comment.
Forgot that convention. Was using it as shorthand for template. Will change.
Sorry, something went wrong.
|
LGTM with some suggestions. |
Sorry, something went wrong.
|
LGTM, other than the comments from Ben. |
Sorry, something went wrong.
Several provider ids have been removed that are no longer in use. Others have been updated to match their class constructors. Add test to ensure all internally listed providers are used. PR-URL: #3139 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-by: Stephen Belanger <admin@stephenbelanger.com>
If the constructor can't assign a class id then the heap snapshot will not be able to report the object. So ensure that all AsyncWrap instances use a FunctionTemplate instance with an internal field count >= 1. PR-URL: #3139 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-by: Stephen Belanger <admin@stephenbelanger.com>
Several provider ids have been removed that are no longer in use. Others have been updated to match their class constructors. Add test to ensure all internally listed providers are used. PR-URL: #3139 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-by: Stephen Belanger <admin@stephenbelanger.com>
If the constructor can't assign a class id then the heap snapshot will not be able to report the object. So ensure that all AsyncWrap instances use a FunctionTemplate instance with an internal field count >= 1. PR-URL: #3139 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-by: Stephen Belanger <admin@stephenbelanger.com>
|
landed in v4.x-staging in e561585...39b8730 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This is long overdue maintenance on AsyncWrap. More PRs will follow, but segmenting to keep reviews simple.
R=@bnoordhuis
R=@indutny
CI: https://ci.nodejs.org/job/node-test-pull-request/405/
CI: https://ci.nodejs.org/job/node-test-pull-request/406/