test(cabq): qc validation for cabq local frost load - #43
Merged
njones-icasa merged 1 commit intoAug 20, 2026
Merged
Conversation
…erted in dlt_pipeline.py
Contributor
|
Your pull request is automatically being deployed to Dagster Cloud.
|
njones-icasa
changed the title
njones-icasa
changed the title
chasetmartin
approved these changes
Aug 20, 2026
likithabommasani21
approved these changes
Aug 20, 2026
njones-icasa
deleted the
ST2DAT-127-test-cabq-QC-validation-for-CABQ-local-FROST-load
branch
August 20, 2026 20:24
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
cabq/dlt_pipeline.pycorrectly translates back and forth between date formats given in 'YYYY-MM-DD' and unitx timestamps in either seconds or milliseconds.Notes
Any special considerations, workarounds, or follow-up work to note?