webui shows CrashLoopBackOff confusingly
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
This seems like a regression or slightly different case of #4258
Steps to Reproduce
- check out servantes
- edit hypothesizer/app.py and add some gobbledygook to make it invalid python (I put
asdfon the first line of theif __name__ == 'main'block) tilt up hypothesizer- open the web ui
- go to the hypothesizer resource view and click on "Errors (1)"
Expected Behavior
When the web ui error filter says there's an error and I click on it, it shows an error
Current Behavior


- every time the pod crash loops, the filters at the top briefly flicker to "Errors (0) Warnings (1)" and then back to "Errors (1) Warnings(0)"
- When I click on "Errors (1)", the log is blank.
Context
tilt doctor Output
$ tilt doctor
Tilt: v0.20.2-dev, built 2021-05-10
System: darwin-amd64
---
Docker
- Host: [default]
- Version: 1.41
- Builder: 2
---
Kubernetes
- Env: kind-0.6+
- Context: kind-kind
- Cluster Name: kind-kind
- Namespace: default
- Container Runtime: containerd
- Version: v1.18.2
- Cluster Local Registry: {Host:localhost:50380 hostFromCluster: SingleName:}
- ```
#### About Your Use Case
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
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 servantes/hypothesizer/app.py by making the Python invalid, then run tilt up hypothesizer and inspect the web UI resource view. Trace the Errors filter and selected log view; done means clicking “Errors (1)” shows the crash-loop error without the filter flickering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes, python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100