[ftr/asyncInstance] fix error thrown for undefined provider instances #22689
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.
When a FTR service is created async the promise created by its provider is wrapped in a
Proxy
that checks before each property access if the instance has finished initializing. This breaks if the service provider returns undefined, which is the case for thefailureDebugging
service, because our truthy check will fail and we throw the error claiming the service is uninitialized, which is probably incorrect.This PR updates the proxy to use a
Symbol
to indicate when a service instance is not available yet and throws a different error when the proxy receives any request (get, set, etc.) and the service instance is not an object, as required by the Reflect APIs.