Search before asking
Apache SkyWalking Component
UI (apache/skywalking-booster-ui)
What happened
In version 10.2.0, for a simple trace like "A calls B and C," the UI shows 5 nodes instead of the expected 3. The API correctly returns 3 spans, but it seems the frontend logic incorrectly attaches each segment group to the root, creating a broken tree.
What you expected to happen
I hope these detailed suggestions are helpful for locating and fixing the bug. I am willing to contribute or create a Pull Request if I can get some guidance from the team.
How to reproduce
The issue is reproducible in any scenario involving multiple segments.
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
Search before asking
Apache SkyWalking Component
UI (apache/skywalking-booster-ui)
What happened
In version 10.2.0, for a simple trace like "A calls B and C," the UI shows 5 nodes instead of the expected 3. The API correctly returns 3 spans, but it seems the frontend logic incorrectly attaches each segment group to the root, creating a broken tree.
What you expected to happen
I hope these detailed suggestions are helpful for locating and fixing the bug. I am willing to contribute or create a Pull Request if I can get some guidance from the team.
How to reproduce
The issue is reproducible in any scenario involving multiple segments.
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct