Q1 2026: Merge activeHandles and activeRequests into activeResources #2149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refs https://jsw.ibm.com/browse/INSTA-64143
refs https://jsw.ibm.com/browse/INSTA-64277
https://nodejs.org/api/deprecations.html#dep0161-process_getactiverequests-and-process_getactivehandles
We previously used the internal methods to get active requests and active handles
These functions are officially deprecated and the official public fn getActiveResourcesInfo exposes the signals together.
Its too much effort to determine which signal belongs to which category (request or handle).
Decided to just return the full number of active resources
BE + client migration first
manually test if that breaks anything (backend / UI)