-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: asm.js type error in latest 1.61.0 version #5992
Comments
did it work in the previous version? |
Hi @yurishkuro I was unable to make 1.60 work. I could not make it accept traces from open telemetry collector :( it works like a charm with 1.61.0 (ingestion). |
Hi @GrzegorzDrozd is this issue resolved, now? |
Hi, I finally got back to this. I see issue on 2.1.0 in both Firefox and on Chrome: |
Confirmed the issue w/ v2.1.0 @anshgoyalevil any ideas what could be causing this? The error seems all over Google, but I don't see a common root cause. |
This is caused by The viz.js version used by Plexus might be deprecated and using Node 12, which according to other repositories is harmless. This error doesn't seem to be related to the zoom/pan not working on the TraceDiff page. |
@anshgoyalevil thanks for the tips. We have an active PR to upgrade viz.js, so perhaps this error will go away. And for panning I will bring it up as part of the LFX project. |
I assume that Pan and zoom on trace compare fix did not make it to 2.2.0 ? |
No , just missed it |
What happened?
Entering trace compare page produces error in javascript console.
I am unable to pan, zoom or do anything in the graph.
Steps to reproduce
Expected behavior
Do not see errors in js console.
Relevant log output
Screenshot
Firefox, after pretty printing, highlights this line:

Additional context
No response
Jaeger backend version
1.61.0
SDK
Docker compose:
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
docker compose
Deployment configs
No response
The text was updated successfully, but these errors were encountered: