Searching spans in a trace page doesn't work

[RotemKir]

Describe the bug
Open a specific trace and enter a span id in the "Find..." textbox does nothing.

To Reproduce
Steps to reproduce the behavior:

1. Open a trace in jaeger ui.
2. Enter a span id in the "Find..." textbox.
3. The url in the browser is updated with the "uiFind=..." parameter but the relevant span isn't marked or found.
4. Refreshing the screen or navigating to the updated url finds the span.
5. No errors were shown in the browser dev tools console, no http errors or calls were made.

Expected behavior
When searching a span id the span should be marked and found (nice to have: a message if nothing was found).

Screenshots
Entering span id (nothing happens):

Refreshing the screen with the same url:

Version (please complete the following information):

• OS: Windows (for the browser), linux for the jaeger backend
• Jaeger version: all-in-one 1.25.0, jaeger UI version 1.15.0
• Deployment: local docker (docker desktop) or in kubernetes

What troubleshooting steps did you try?

1. Didn't see any errors in the dev tools console.
2. Didn't see any http calls (should be fine I guess since the search is probably done in the client side).
3. Couldn't find any existing issue open in github related to this.

Additional context
IIRC the search worked fine a few versions earlier, can't recall which version since I upgraded the docker image several times in the past month.
As a workaround refreshing the screen or navigating directly to the url with the trace and span ids works, just searching in the page seems broken.

[ndrscodes]

@RotemKir Can confirm in 1.25.0, the issue is also present in jaeger 1.24.0.

[ndrscodes]

I am a backend dev so i really have no real clue about react, but i'm pretty sure focusSpan() is never actually called and the span query is never updated. Passing the uiFind parameter in the URL unlocks the search menu buttons on the side, but once you use them, the input on the side is reset to the previously found span ID.
Maybe that helps someone with react experience fix the issue :)

[w0wka91]

I will take a look at this bug if thats okay with you guys?!
Or is someone else already working on this issue?

[albertteoh]

Yup, I'm able to reproduce with the latest build as well.

No one has claimed this so it's yours, @w0wka91 :)

[w0wka91]

The problem is related to incompatible versions of react-router-redux and react-router-dom.
At the moment we are using react-router-dom 5.2.0 which is not compatible with react-router-redux 5.x (https://www.npmjs.com/package/react-router-redux/v/5.0.0-alpha.8)
I was able to fix the problem by downgrading react-router-dom to 4.3.1

[vvvprabhakar]

Any update on this ?

[yurishkuro]

being addressed in #837