provectus/kafka-ui

FE: Do not show messages behind = 0, when it is not set on backend

Open

#4,144 opened on 2023年8月22日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)Java (7,799 stars) (977 forks)batch import
good 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 on Consumers page if consumer has no committed offsets, now it is show like message behind = "0", which is not right.

Expected behavior

No value should be shown. (of disclaimer that "No offsets have been committed yet")

Your installation details

0.7.1

Steps to reproduce

  1. start consumer that reads any topic
  2. go to Consumers -> select consumer -> see messages behind column (on topic level)

Screenshots

Logs

No response

Additional context

No response

コントリビューターガイド

技術スタック
reacttypescript
領域
frontend
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
2
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
under 1 hour
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Basic React knowledgeUnderstanding of Kafka consumer offsets
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
80
調査方針
Look at the frontend code for the Consumers page, specifically the component that displays the 'messages behind' column. Search for where the value 0 is shown for uncommitted offsets. The fix likely involves checking if offsets are committed before displaying 0, or showing a placeholder message. Check the comments on the issue for any additional context or hints from maintainers.