-
Notifications
You must be signed in to change notification settings - Fork 237
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
[BUG] SharedWorker does not Instrument fetch correctly #1996
Labels
Milestone
Comments
MSNev
added
p1
service-worker
Required to properly support service workers
shared-worker
labels
Feb 17, 2023
Assigned to 2.8.11 so we can attempt to address in v2 which will them also get merged to v3 (beta) |
MSNev
added a commit
to MSNev/ApplicationInsights-JS
that referenced
this issue
Feb 23, 2023
…ft#1996 - Also add a Shared Worker example
MSNev
added a commit
to MSNev/ApplicationInsights-JS
that referenced
this issue
Feb 23, 2023
…ft#1996 - Also add a Shared Worker example
MSNev
added a commit
that referenced
this issue
Feb 24, 2023
MSNev
added a commit
that referenced
this issue
Feb 28, 2023
MSNev
added
fixed - waiting release
PR Committed and waiting deployment
waiting - CDN deployment
released - NPM
and removed
fixed - waiting release
PR Committed and waiting deployment
labels
Mar 8, 2023
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
@celluj34 has identified as part of issue #1995 that for a Shared worker the InstrumentFunc for the fetch is not working due to checks around
hasOwnProperty
failing forglobalThis.fetch
and the beta usage ofObject.getOwnPropertyDescriptor
also fails.We need to investigate and add an additional fallback from the
_getOwner()
or equivalent to use either an existence check and/orin
. We also need to validate that even with these checks that we can correctly hook the relevant function and/or prototype.This should be fixed in v2.x (if possible) and v3.x.
The text was updated successfully, but these errors were encountered: