redpanda-data / redpanda-data/console
Setting 'infinite' on certain config values, will set a high value instead
Open
Nobody has claimed this yet.
bug
frontend
low-priority
ui/ux
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
When setting something like max.message.bytes you can choose infinite however, the value is automatically reset to 4Gi as bytes. Its not a big deal but infinite is technically not true. Changing the field to max or something and displaying what that value would be is a little more accurate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating the configuration editor and the handling for max.message.bytes, then reproduce selecting infinite and observing the resulting 4Gi value. Done means the UI no longer presents a finite fallback as infinite and clearly communicates the effective value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100