BE: Null latest release information

[vishal-bihani]

Issue submitter TODO list

• [X] I've looked up my issue in FAQ
• [X] I've searched for an already existing issues here
• [X] I've tried running main-labeled docker image and the issue still persists there
• [X] I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Applicaton information api is returning null latest release information.

Expected behavior

Api should provide the latest release information.

Your installation details

Commit Id: 2956664

Steps to reproduce

Visit the homepage of Kafka-UI

Screenshots

No response

Logs

No response

Additional context

No response

[github-actions[bot]]

Hi vishal-bihani! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues. Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[vishal-bihani]

We should recreate the Mono every single refresh. Once a mono has been successful, subscribing won't provide any results

[Haarolean]

Are there any logs on this matter? Most likely, it could be a request timeout

[kapybro[bot]]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[vishal-bihani]

Are there any logs on this matter? Most likely, it could be a request timeout

No, nothing spotted. kafka-ui-logs.txt

Also default timeout is set to 10 seconds, it is very unlikely. Even if there is timeout, this approach doesn't seem reliable, have written an alternate, have a look: #577

[kapybro[bot]]

Thanks for the additional feedback! We'll get back to your issue soon.

[Haarolean]

@vishal-bihani could you please provide exact steps to reproduce the issue? Before we start looking into the PR, we need to understand what's the issue there.

This works fine for me on different commits (a bit older one and the latest from main) on different environments:

[vishal-bihani]

Sure. Steps:

1. Pull the latest commit.
2. Build the docker image with new tag
3. Replace the current tag of kafka-ui in documentation/compose/kafbat-ui.yaml with the new one
4. Use docker compose to start the kafka cluster and the kafbat

Image with the latest commit:

Image with my commit:

As mentioned in previous commit, with TRACE level enabled, I don't see any timeout errors in the logs.

Device info: OS: MacOS Chip: M1

[Haarolean]

The second screenshot I provided has commit 941358d which is the most recent one from main. Not sure how to reproduce this.

[kapybro[bot]]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[vishal-bihani]

Nothing changed from 8df11ac to 941358d in BE. But I was not able to reproduce in newer versions so closing this issue.

[kapybro[bot]]

Thanks for the additional feedback! We'll get back to your issue soon.