You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the filters say there are errors or warnings selecting on the filter should display them.
Current Behavior
The log area only shows headers of all the resources. I think these are a little misleading and you can probably do without the headers. Especially when there are no errors or warnings to report for that resource.
Steps to Reproduce
Deploy some resources that will throw warnings or errors.
Switch to the new UI .
Click the filter for warning/ error.
Observe the log area.
Context
tilt doctor Output
$ tilt doctor
Tilt: v0.18.9, built 2021-02-12
System: darwin-amd64
---
Docker
- Host: [default]
- Version: 1.41
- Builder: 2
---
Kubernetes
- Env: docker-for-desktop
- Context: docker-desktop
- Cluster Name: docker-desktop
- Namespace: default
- Container Runtime: docker
- Version: v1.19.3
- Cluster Local Registry: none
---
Thanks for seeing the Tilt Doctor!
Please send the info above when filing bug reports. 💗
The info below helps us understand how you're using Tilt so we can improve,
but is not required to ask for help.
---
Analytics Settings
--> (These results reflect your personal opt in/out status and may be overridden by an `analytics_settings` call in your Tiltfile)
- User Mode: opt-out
- Machine: b07ff31bcc0852cb4ed113aa80c93207
- Repo: trjiT0Rdv7yICO5gwAvx0g==
About Your Use Case
Discussed with Han over a zoom call.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When the filters say there are errors or warnings selecting on the filter should display them.
Current Behavior
The log area only shows headers of all the resources. I think these are a little misleading and you can probably do without the headers. Especially when there are no errors or warnings to report for that resource.
Steps to Reproduce
Context
tilt doctor
OutputAbout Your Use Case
Discussed with Han over a zoom call.
The text was updated successfully, but these errors were encountered: