-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Add --exclude-from-upload
and --exclude-from-download
options
#370
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
from nextstrain.cli import make_parser | ||
|
||
|
||
def pytest_build_download_options(): | ||
parser = make_parser() | ||
|
||
opts = parser.parse_args(["build", "."]) | ||
assert opts.download is True | ||
|
||
opts = parser.parse_args(["build", "--no-download", "."]) | ||
assert opts.download is False | ||
|
||
opts = parser.parse_args(["build", "--download", "x", "."]) | ||
assert opts.download == ["x"] | ||
|
||
opts = parser.parse_args(["build", "--download", "x", "--download", "y", "."]) | ||
assert opts.download == ["x", "y"] | ||
|
||
opts = parser.parse_args(["build", "--exclude-from-download", "z", "."]) | ||
assert opts.download == ["!z"] | ||
|
||
opts = parser.parse_args(["build", "--exclude-from-download", "z", "--exclude-from-download", "a", "."]) | ||
assert opts.download == ["!z", "!a"] | ||
|
||
opts = parser.parse_args(["build", "--download", "y", "--exclude-from-download", "z", "."]) | ||
assert opts.download == ["y", "!z"] | ||
|
||
opts = parser.parse_args(["build", "--download", "y", "--download", "!z", "."]) | ||
assert opts.download == ["y", "!z"] |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potentially tangential to this PR
Reading this code my understanding is that only the build directory is uploaded, and so patterns are relative to that. How does this work when the build directory is (e.g.)
ingest/
but within that the Snakefile refers back to a parent directory?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, that's a great point. The directory here that matters—the one that's uploaded and one that patterns must be relative to—is influenced by the
nextstrain-pathogen.yaml
file. For example, runningnextstrain build ingest/
in a directory withnextstrain-pathogen.yaml
will require patterns be relative to the directory containing the marker file, not theingest/
directory, i.e. to exclude something iningest/
would require the pattern to beingest/x/y/z
not justx/y/z
.I'll update the docs here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I want to leave the option docs/help as-is for now for this PR. I'm realizing there's larger documentation reworking to do to clarify terminology here as a result of #355 (something I'd postponed in that PR). Writing a clear help snippet for these pattern options will be much easier and less inconsistent/confusing once the larger terminology shift and doc updates happen. I should prioritize that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#371
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 totally forgot about this subtlety. Is this behaviour mirrored in what directories are bind-mounted into the docker container (when running locally)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep.
Before #355 the directory given to
nextstrain build
ended up as/nextstrain/build
in the container and/nextstrain/build
was the fixed working directory for the container process.After #355, the
/nextstrain/build
mount is either the directory given tonextstrain build
or, if present, the closest ancestor of the given directory which contains anextstrain-pathogen.yaml
. The working directory for the container process is the/nextstrain/build
path corresponding to the directory given tonextstrain build
.