tiltfile: fix ignores if context dir appears later #6467
+0
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Consider the following (admittedly somewhat unusual) Tiltfile:
This implements on-demand git cloning — the clone happens during the build phase of the resource, and thus other builds can proceed concurrently and this may speed up overall tilt up (and it does in the quite complex tilt setup that we have).
In current Tilt, however,
ignore
andonly
are completely ignored if the context directory doesn't exist when the Tiltfile is loaded. This is quite a strange and seemingly pointless limitation, as everything else seems to work fine.The fix is trivial — simply remove the IsDir check from
dockerignoresFromPathsAndContextFilters
. The code that follows the check handles the absence of the dockerignore files just fine, so it seems the IsDir check is simply forgotten there from previous iterations.Note that a similar issue exists in the
repoIgnoresForPaths
function as well. The Tiltfile to reproduce that problem is the same, just without theignore = ["**/.git"]
bit. I'm not entirely sure if thatisGitRepoBase
check serves any real purpose — would there be any harm if ".git" was ignored unconditionally (well, we'd need to check for the empty path likedockerignoresFromPathsAndContextFilters
does)?Related: #3048 (comment)