fix(core): Ensure _tick is always run within the TracingSnapshot. #58881
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Ensures that _tick will always run within a TracingSnapshot if one has been requested. _tick is run directly from zoneless_scheduling_impl.ts which bypasses tick().
Issue Number: N/A
What is the new behavior?
This ensures that all calls to _tick run within the Snapshot which enables to the underlying tracing implementation to release the snapshot.
Does this PR introduce a breaking change?
Other information