You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the XHR plugin, each reported span after the reporting throws the error: "Uncaught (in promise) ReferenceError: can't access lexical declaration 'promise' before initialization". Console exporter works without any issue.
What did you expect to see?
No error is thrown.
What did you see instead?
Unhandled error in dev. console.
Additional context
Firefox 81.0.2.
Here is a stack trace.
Uncaught (in promise) ReferenceError: can't access lexical declaration 'promise' before initialization
_onFinish CollectorExporterBrowserBase.js:64
_onSuccess CollectorExporterBrowserBase.js:57
sendWithBeacon util.js:29
promise CollectorExporterBrowserBase.js:72
send CollectorExporterBrowserBase.js:54
_export CollectorExporterBase.js:70
_export CollectorExporterBase.js:67
export CollectorExporterBase.js:52
onEnd SimpleSpanProcessor.js:44
with StackContextManager.js:103
with context.js:60
onEnd SimpleSpanProcessor.js:43
onEnd MultiSpanProcessor.js:51
end Span.js:134
endSpanTimeout xhr.js:253
endSpan xhr.js:271
The text was updated successfully, but these errors were encountered:
Sebosek
changed the title
OpenTracing collector exporter throws ReferenceError after trace export
OpenTracing collector exporter throws ReferenceError after trace export in Web application
Oct 21, 2020
Please answer these questions before submitting a bug report.
What version of OpenTelemetry are you using?
0.12.0
What version of Node are you using?
v12.18.3
Please provide the code you used to setup the OpenTelemetry SDK
opentelemetry.js
docker-compose.yaml
collector-config.yaml
What did you do?
I'm using the XHR plugin, each reported span after the reporting throws the error: "Uncaught (in promise) ReferenceError: can't access lexical declaration 'promise' before initialization". Console exporter works without any issue.
What did you expect to see?
No error is thrown.
What did you see instead?
Unhandled error in dev. console.
Additional context
Firefox 81.0.2.
Here is a stack trace.
The text was updated successfully, but these errors were encountered: