bug: CLI hangs indefinitely during network failures due to missing `http.Client` timeouts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- cli, networking
Research direction
Trace the CLI's internal HTTP client initialization and reproduce the hang with the start or simulate command against an unresponsive Microcks or Keycloak server. Set a 30-second client timeout and verify that the command returns a helpful timeout error instead of waiting indefinitely.
Written by the indexing model from the issue text.
Description
Describe the bug
The CLI currently initializes its internal HTTP clients without explicitly setting a Timeout field. In Go, an http.Client without a configured timeout (or when using http.DefaultClient) will default to waiting infinitely. If a network connection silently drops, or if the Microcks/Keycloak server is locked up and unresponsive, the CLI freezes forever in the terminal and must be manually killed by the user.
Expected behavior
The CLI should fail fast with a helpful connection timeout error (e.g., context deadline exceeded or timeout) if the server takes longer than 30 seconds to respond, returning control to the user.
Actual behavior
The CLI hangs infinitely in the terminal with no output.
How to Reproduce?
Try with start or simulate it.
Microcks version or git rev
No response
Install method (docker-compose, helm chart, operator, docker-desktop extension,...)
No response
Additional information
No response
- Dominant language
- Go
- Stars
- 57
- Forks
- 72
- Avg merge
- 1d 35m
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from microcks/microcks-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microcks/microcks-cli#561 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microcks/microcks-cli#559 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microcks/microcks-cli#554 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
microcks/microcks-cli#551 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microcks/microcks-cli#536 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microcks/microcks-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
lightninglabs/lndmon#140 ·
-
documentation good first issue ready-for-triage ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
release-engineering/fbc-update-planner#102 · 3 comments ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yetone/magpie#562 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 4 days