-
Notifications
You must be signed in to change notification settings - Fork 16
Analysts see labeled GTFS Schedule processing steps #4548
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
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
70cfd4b
Analyst sees valid GTFS Schedule pipeline data
erikamov b1c0f27
Skip empty source files
erikamov 143d9a5
Fix unzip and convert fanout
erikamov cc96146
Upload only the report when the file when empty
erikamov 37e1a6a
Parse only extracted files
erikamov 72b6a60
Use a friendly name on create kwargs and label
erikamov 567b38f
Fix Empty content file tests
erikamov cc77e2e
Test empty unzipped file
erikamov 1bffc23
Fix date on Validation skips and tests
erikamov 15fddff
Analyst sees a consolidated GTFS Schedule unzip and parse workflow
erikamov e543572
Retries only one time
erikamov 055a70a
Allow notices to be empty
ohrite 87cbd00
Allow Content-Disposition headers to not have filenames
ohrite c23b876
Test validating an empty (unsupported) GTFS zip file
erikamov 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
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.
Question -- maybe for a follow-up: Is it worth revisiting these variable names if they no longer correspond to the DAG task names? (
_HOURLYsuffix likely to be confusing for future users?)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, on the new branch I added labels to all map indexes ;) Loved it too!!
Still testing so more to come.
For sure when we delete the hourly DAGs we will rename those buckets, but for now it is the same to make sure we are using the same data and files.