tilt-dev / tilt-dev/tilt

`tilt down` hangs when offline due to git pull in extension directory

Open
#6,546 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs repro case
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Expected Behavior

I should be able to run tilt down regardless of my internet connection status.

Current Behavior

When I try to run tilt down while offline, the command gets stuck. It appears to be attempting the following behind the scenes before executing command hooks or proceeding with the normal teardown process:

cd "$LIBRARY_DIR/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions"; git pull

Steps to Reproduce
  1. Run tilt up on a Tiltfile that uses extensions (while online)
  2. Disconnect from the internet
  3. Run tilt down
Context
Tilt: v0.34.2, built 2025-04-09
System: darwin-arm64
---
Docker
- Host: unix:///var/run/docker.sock
- Server Version: 26.1.5
- API Version: 1.45
- Builder: 2
- Compose Version: v2.33.0
---
Kubernetes
- Env: rancher-desktop
- Context: rancher-desktop
- Cluster Name: rancher-desktop
- Namespace: default
- Container Runtime: docker
- Version: v1.30.11+k3s1
- Cluster Local Registry: none
About Your Use Case

I was just trying to work outside the office, offline. Ideally, tilt down should still work in this scenario without getting blocked by a failed network operation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the tilt down entry point and teardown flow, focusing on the extension directory operation that runs git pull. Reproduce the issue offline after tilt up with an extension, then verify that tilt down proceeds with command hooks and normal teardown without blocking on the network operation.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.