FE: Handle 504s properly · provectus/kafka-ui#4075

(4 评论) (0 反应) (0 负责人)Java (7,799 star) (977 fork)batch import

area/uxgood first issuescope/frontendstatus/acceptedtype/bug

描述

Issue submitter TODO list

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

Describe the bug (actual behavior)

when kafka-ui can't access the remote broker, it waits for a long time (this should also have timeout). Meanwhile in the UI you see the loader in the topics page.

In the network tab I can see long request:

http://server/api/clusters/<cluster>/topics?page=1&perPage=25&showInternal=true

At some point it fails with 504, but the loader is still shown on the UI

Expected behavior

Loader should be removed and the error message should be shown

Your installation details

56fa824

Steps to reproduce

make sure kafka ui can't access remote broker.
visit topics page in that cluster

Screenshots

No response

Logs

no logs in the app output

Additional context

No response

贡献者指南

技术栈: 无
领域: frontend
议题类型: bug
难度: 2
预计时间: 1-3 hours
活动状态: fresh
清晰度: mostly clear
前置要求: Basic frontend developmentUnderstanding of HTTP error handling
新手友好度: 75
研究方向: Investigate the frontend's API request handling, likely in the Topics page component. Look for where the loader is controlled and add error handling for 504 responses to display an error message instead of keeping the loader. Check if there is an existing error state pattern in the codebase, possibly in the network layer (e.g., axios interceptors) or within the component itself. Reference the commit 56fa824 if available.