LiveUpdate does not finish with Pending after switching the trigger mode from manual to auto.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, docker-compose, go
- Domain
- developer-experience, devtools
Research direction
Start with the linked reproduction repository and follow the WebUI transition from manual to auto for the app resource, then reproduce the file update with touch server.js. Trace why LiveUpdate remains Pending after that transition; done means the update triggers and finishes successfully instead of staying Pending.
Written by the indexing model from the issue text.
Description
Expected Behavior
LiveUpdate is triggered and finished successfully when files are updated.
Current Behavior
The resource is pending and does not finish.
Steps to Reproduce
- Run the following resource with Tilt. (I have the code to reproduce based on a tutorial. here.)
- with docker-compose
- with live update
- with manual trigger
-
In the WebUI, change the trigger mode of
appfrom manual to auto.
-
Update a file of
appresource as follows.
$ touch server.js
-> LiveUpdate of app resource does not finish with Pending.
Context
tilt doctor Output
$ tilt doctor
Tilt: v0.32.0, built 2023-03-13
System: darwin-arm64
---
Docker
- Host: unix:///Users/suzuki.yoshiharu/.docker/run/docker.sock
- Server Version: 20.10.23
- API Version: 1.41
- Builder: 2
- Compose Version: v2.15.1
---
Kubernetes
- Env: docker-desktop
- Context: docker-desktop
- Cluster Name: docker-desktop
- Namespace: default
- Container Runtime: docker
- Version: v1.25.4
- 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-in
- Machine: e4f1d3c3e5e32ef82408eec45fb2f2a1
- Repo: N0bjDegm65kAF+Q2vFT8zQ==
About Your Use Case
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
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.
More from tilt-dev/tilt
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Tilt at scale Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100