Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Miovision anomalous ranges creates unexpected results when run out of order #1143

Open
1 of 2 tasks
gabrielwol opened this issue Feb 4, 2025 · 0 comments · May be fixed by #1145
Open
1 of 2 tasks

Miovision anomalous ranges creates unexpected results when run out of order #1143

gabrielwol opened this issue Feb 4, 2025 · 0 comments · May be fixed by #1145
Assignees
@gabrielwol
Labels
bug Miovision

Comments

@gabrielwol
Copy link
Collaborator

gabrielwol commented Feb 4, 2025 •
edited
Loading

Over the weekend we had a situation where Feb 1 and Feb 2 failed. I then fixed+reran Feb 1 but forgot about Feb 2, so they ran in this order: Feb 1 -> Feb 3 -> Feb 2. It resulted in a bunch of new anomalous ranges that start on Feb 3 with the old ones ending on Feb 3.
We can fix this by:

  • adding depends_on_past=True to that task
  • manually combining those ranges.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gabrielwol gabrielwol

Labels
bug Miovision
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#1143 depends_on_past=True, remove unused imports CityofToronto/bdit_data-sources
1 participant
@gabrielwol