redpanda-data / redpanda-data/console
Several Kafka Connect pages crash browser with infinite loop
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
See attached videos.
Simply clicking on the cluster name triggers a mobx infinite loop and you can't click anything on the page. Eventually Chrome kills the tab. Note: This happens in Firefox and Safari as well.
https://github.com/user-attachments/assets/9b1a461c-1d70-4278-88f7-ed3bf9beace0
If you click on the "Connectors" tab, you can see that the components are infinitely rerendered. The page doesn't crash, but you also can't click on any of the connectors I guess due to them being rerendered so frequently.
https://github.com/user-attachments/assets/37a57271-7a30-4f68-84c9-36c11225a2d6
Currently running it as such:
redpanda-console:
image: docker.redpanda.com/redpandadata/console:v3.1.1
entrypoint: /bin/sh
command: -c 'echo "$$CONSOLE_CONFIG_FILE" > /tmp/config.yml && /app/console'
volumes:
- ./config:/tmp/config/
environment:
CONFIG_FILEPATH: ${CONFIG_FILEPATH:-/tmp/config.yml}
CONSOLE_CONFIG_FILE: |
kafka:
brokers: ["kafka:9092"]
schemaRegistry:
enabled: true
urls: ["http://schema-registry:8085"]
kafkaConnect:
enabled: true
clusters:
- name: kafka-connect
url: http://connect:9031
console:
topicDocumentation:
enabled: true
git:
enabled: true
repository:
url: https://github.com/redpanda-data/docs
branch: main
baseDirectory: tests/docker-compose
ports:
- 9032:8080
profiles: ["kafka"]
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
Reproduce the issue with the provided Docker Compose configuration, then inspect the Kafka Connect cluster page after clicking the cluster name and the Connectors tab. Done means both pages remain responsive without infinite MobX rerenders or browser-tab crashes, including in Firefox and Safari.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100