Skip to content
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

Span bar broken on click #628

Closed
Stono opened this issue Aug 26, 2020 · 10 comments
Closed

Span bar broken on click #628

Stono opened this issue Aug 26, 2020 · 10 comments

Comments

@Stono
Copy link

Stono commented Aug 26, 2020

Hey,
I've just excitedly deployed 1.19 (which has ui version 1.10) due to it having a fix for the span hover issue (#599).

Whilst that has been fixed, there's another bug now that when we click spans sometimes they load empty:

Screenshot 2020-08-26 at 17 35 35

On top of that sometimes multiple spans expand when you click one of them:

Screenshot 2020-08-26 at 17 37 31

So unfortunately all in all its even worse than 1.18!

I'm on chrome 84.0.4147.135 however it's the same on safari too.

@yurishkuro
Copy link
Member

cc @rubenvp8510

@robinator8
Copy link

Reproduced on Ubuntu 18.04.4 LTS:

  • chrome version 84.0.4147.135
  • Firefox version 79.0

@Azim-Palmer
Copy link

Reproduced on Windows

  • chrome version 84.0.4147.135

@objectiser
Copy link
Contributor

@everett980 @tiffon Any chance you could take a look? @rubenvp8510 is on PTO until Monday.

@yurishkuro
Copy link
Member

@tklever I suspect it's the React refactoring that caused this issue. I reverted the UI prior to your first change and it seems to work.

@tklever
Copy link
Contributor

tklever commented Aug 27, 2020

Oh no! Let me know what you find, maybe I can get some tests around it to ensure it doesn't regress further

@yurishkuro
Copy link
Member

Sadly we don't have anyone available at the moment to troubleshoot this (people are on vacations). The reported issue is easily reproduced - running all-in-one (which does self-tracing), and then expanding any span shows the blank space. I suspect one of those callback methods isn't being called at the right time, since the renaming wasn't semantically fully equivalent.

@tklever
Copy link
Contributor

tklever commented Aug 27, 2020

It's #612 that causes it. I'll keep digging to get more specific / find a fix.

@tklever
Copy link
Contributor

tklever commented Aug 27, 2020

Specifically it's the changes in #612 to packages/jaeger-ui/src/components/TracePage/TraceTimelineViewer/VirtualizedTraceView.tsx, reverting just that file gets rid of the emptiness.

Looks like @rubenvp8510 already has a fix.

@Stono
Copy link
Author

Stono commented Aug 27, 2020

Just tested on 1.19.2 btw and can confirm all is well

@Stono Stono closed this as completed Aug 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants