Tilt up `--hud` looks broken
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Expected Behavior
the cmd line docs for tilt up --hud seem to indicate it is default true... which should be the default tilt up. however it looks identical to tilt up --legacy. In addition, I would expect a validation error for tilt up --legacy --hud as those should be mutually exclusive.
Current Behavior
Currently --hud looks like --legacy and not like the default.
Steps to Reproduce
tilt up --hud
Context
This is off HEAD of master... sha at this moment: 057bf28ad6f4e00a80addbe304f128d1439d4513
tilt doctor Output
Tilt: v0.24.0-dev, built 2022-02-05
System: darwin-arm64
---
Docker
- Host: [default]
- Server Version: 20.10.12
- API Version: 1.41
- Builder: 2
- Compose Version: v1.29.2 (build 5becea4c)
---
Kubernetes
- Env: kind-0.6+
- Context: kind-kind
- Cluster Name: kind-kind
- Namespace: default
- Container Runtime: containerd
- Version: v1.21.1
- Cluster Local Registry: none
---
...
About Your Use Case
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
Start by reproducing tilt up --hud and tilt up --legacy --hud from the tilt up command entry point, comparing both with plain tilt up. Trace the CLI flag handling and documentation referenced in the issue; done means --hud matches the default behavior and the mutually exclusive combination returns a validation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100