-
Notifications
You must be signed in to change notification settings - Fork 4
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
FEAT: Write Bus Performance metrics to S3 Bucket #451
Conversation
Coverage of commit
|
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.
👍 Just one tiny question.
I appreciate the PR description.
In the future, if it's possible to separate out things like this formatting change into an isolated PR or commit, that would make it easier to quickly rubber stamp that bit and better understand which are the functional changes worth looking closer at.
""" | ||
Test that bus routes be generated for a given service date. For the | ||
generated list ensure | ||
* they don't contain Subway, Commuter Rail, or Ferry routes | ||
* don't have a leading zero | ||
* contain a subset of known routes | ||
""" | ||
assert True | ||
exists_patch.return_value = True |
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: Does this still need the assert
?
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. That assert is essentially a no-op. My guess is that it was in there as a place-holder before the full test function was written, and then it was never removed.
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.
👍 got it. I also spaced out on the single vs double =
.
This change creates real-time bus performance parquet files and writes them to a partition on the S3
PUBLIC_ARCHIVE_BUCKET
.This process has been successfully run locally (using staging bucket data) and on the
dev
environment.Files are generated for each service date with the following steps:
RT_VEHICLE_POSITION
springboard filesTM/STOP_CROSSING
springboard filesThis PR also contains a linting change that increases minimum line length from 80 to 120 lines, so many files are no-op formatting changes.
Asana Task: https://app.asana.com/0/1205827492903547/1208021735441632