Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix: Deep clone trace data for consistency (#2571)
Resolves #2483 ## Description of the changes - deep cloned the trace data before passing it to @pyroscope/flamegraph ## How was this change tested? - npm run test - visual comparison with this traces data [trace.zip](https://github.com/user-attachments/files/18364826/trace.zip): Timeline view: ![timeline](https://github.com/user-attachments/assets/52f3e039-0ef9-40e9-9461-69e3c3867995) Flamegraph view: ![flamegraph](https://github.com/user-attachments/assets/e68110e1-e26a-4a09-99b3-beb99ebc5275) Navigating back and forth between flamegraph and timeline views no longer show inconsistent data ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [ ] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `npm run lint` and `npm run test` --------- Signed-off-by: Kaung Zin Hein <[email protected]> Signed-off-by: Kaung Zin Hein <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
- Loading branch information