Repository navigation
doc: acknowledge process._getActiveHandles() and process._getActiveRequests() #36036
Description
Activity
It seems that it has been stalled, would you like me to consider to pick it up?
As far I can understand, it's only ref change, and adding docs isn't it?I would love to have some help from documentation on how I can see what is in the event loop. Can someone pick this up so a lowly programmer like me can better understand and debug concurrency issues that currently seem more like black magic than science to me?
Someone would need to revive one of the earlier attempts and resolve the outstanding issues.
Speaking for myself (but also as the one who introduced those methods), I don't think they're all that useful actually to most users. There is no 1-to-1 correspondence between libuv handles and JS objects.
I'm going to close this issue because it's approaching its three year anniversary without movement but a PR is still welcome, just don't expect it to get merged without additional discussion.
📗 API Reference Docs Problem
Location
Section of the site where the content exists
Affected URL(s):
Description
Concise explanation of the problem
I believe the functions process._getActiveHandles() and process._getActiveRequests() should be documented, and be acknowledged; We should consider adding non-dashed alias as it is used for some time in the ecosystem.
Currently there are packages which rely at those methods. Even if they will be considered for removal, a regular deprecation process should be considered.
Alternatively, a consensual interface should be considered, if there is a reason for which, the functions aren't documented.
Anyway, as the functionality is in use and appears time to time in the community, we should embrace these functionalities, as part of the standard documented node features.
submit a pull request.
? question mark stands for "it depends".