-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Update nightly build script to quietly publish public Parquet outputs. #3680
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
ba814dc
Update nightly build script to quietly publish public Parquet outputs.
zaneselvans 1cf2909
Remove unnecessary path element.
zaneselvans 953f7d7
Clarify comments
zaneselvans c0a1dbd
Remove ~200 parquet files before Zenodo data release
zaneselvans c55b66b
Merge branch 'main' into quiet-parquet
zaneselvans b9d708e
Merge branch 'main' into quiet-parquet
zaneselvans 0903a15
Use pushd/popd instead of cd in build script.
zaneselvans c838354
Simplify parquet file deployment a little
zaneselvans 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
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.
Is this for loop going to break the chain of
&&
dependencies and mess up our exit codes?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.
I don't think so: the
&&
operator just glues two things together with the boolean AND as far as I know. Though I'm not sure if there will simply be a syntax error here.One way around this would be just "pull the compression logic into its own function."
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.
I thought what was being ANDed together was the exit codes? So if they're all 0, then the exit code for the whole chain of codes ends up being 0, but if any of them is non-zero, then the remaining commands are not executed, and the exit code ends up being whatever nonzero value the failing command issued?
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.
Yeah, I think the exit codes are the things that are being ANDed together. We're using the short-circuiting behavior of
&&
to say that each expression only executes if everything to its left returns 0.But we have several separate
&&
-chains, and we don't exit immediately if one of the chains themselves has a non-0 return value. I think that's intentional so we can make the slack notifications at the end.The body of the for loop is its own
&&
-chain because we don't have&&
afterrm "$file"
- so in my mental model, a failure inzip
would stop us from trying torm "$file"
but we would effectively just skip over that file completely.