-
Notifications
You must be signed in to change notification settings - Fork 4.6k
fix(trace): Reload traces immediately on service worker start #37551
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cpAdm
wants to merge
1
commit into
microsoft:main
Choose a base branch
from
cpAdm:fix-reload-traces-on-sw-restart
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we want all the traces to be loaded for inactive clients. I think we want to move the
if (!clientIdToTraceUrls.has(event.clientId)) {
block of the original code up in doFetch and omit it for /context.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Although that would mean that if the first request after a reload is a
/trace/snapshot
call, the trace is not reloaded (since this is a different client worker (event.clientId
) then the one that called/contexts
) and we still return 404. Right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also we have to think about scenarios like:
/ping
, it willgc
and remove traces (params in IndexDB) for all other clients.Sidenote: How important is the
gc
? Isn't the browser already taking care of this by shutting down the SW? (we can always do theawait self.clients.matchAll();
check whenever the SW restarts)Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The GC is so that you could open 100 traces one after another in the same window (UI Mode) without exploding out of memory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it a different client worker? I assume event.clientId are preserved, so should return the right value.
Why does gc remove traces for all other clients? I would assume that once the sw is restarted, self.clients.matchAll() would return them and no gc will happen?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should have been more clear here. What I meant is that each tracer viewer has two clients: one for the trace viewer itself (which also loads the trace) and one for the iframe (which fetches
/snapshot
). They have differentevent.clientId
s (but indeed on a restart their Ids remain the same).But I actually don't think it is currently possible for the
/snapshot
call to arrive first after a SW restart (itsclientId
is not linked to a saved trace). Since when selecting an action in the trace viewer, always first a/snapshotInfo
call will be made (which reloads the trace). Then after that the/snapshot
call is made, but at that time the trace has thus already been reloaded.