We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Corresponding issue in the backend: jaegertracing/jaeger#3958
i guess the package 'isomorphic-fetch' may loss of precision(int64) while proxy to load data from jaeger jaeger-ui: v1.14.0 jaeger: v1.24.0
6.we can find out the value of "liveroom_sid" changed 780177723283783680 -> 780177723283783700
jaeger : response int64 value "780177723283783680" jaeger-ui: receive int64 value "780177723283783680" (but it shows "780177723283783700" )
No response
v1.24.0
The text was updated successfully, but these errors were encountered:
sorry, my bad. this bug is because 780177723283783680 overflow js Number.MAX_VALUE to cause precision loss,and i change the code
will fix this, but it will copy bigint as string because of GoogleChromeLabs/jsbi#30
plz let me know it if there is better way to fix this situation
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Corresponding issue in the backend: jaegertracing/jaeger#3958
What happened?
i guess the package 'isomorphic-fetch' may loss of precision(int64) while proxy to load data from jaeger
jaeger-ui: v1.14.0
jaeger: v1.24.0
Steps to reproduce
4.access /trace/4c5d7a066c367635704f06207dd56b45 page
5.aceess api directly
6.we can find out the value of "liveroom_sid" changed
780177723283783680 -> 780177723283783700
Expected behavior
jaeger : response int64 value "780177723283783680"
jaeger-ui: receive int64 value "780177723283783680" (but it shows "780177723283783700" )
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
v1.24.0
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: