-
Notifications
You must be signed in to change notification settings - Fork 9
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
Do not unregister datasets with a 404'ed base schedule at time of startup #109
Conversation
Co-authored-by: Antoine D <antoine.desbordes@gmail.com>
For now, just a failing test to reproduce the issue has been added, to start playing around. |
we can remove the draft mode no? I found a way to hide the |
@antoine-de sorry, I just understood now what you meant by removing the draft mode, thought you were referring to something in the code. I've moved out of draft mode, thanks! |
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.
great!
As seen in #107, if at start time, a given resource is not available, it will be removed from the available resources forever.
In this PR, we instead implement a mechanism to ensure the initial failure has a chance to recover later.
It must be noted thought that it will currently take 24 hours before the dataset is retried (see #111), something we will improve in a separate PR.