-
Notifications
You must be signed in to change notification settings - Fork 31
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
implement failed strategy #77
base: master
Are you sure you want to change the base?
Conversation
minor conflict to be cleaned up and I'll get this merged |
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 think the querying in this strategy is going to need a bit more machinery (most of which I'm inclined to have tested to be sure we're actually doing things correctly).
First, I worry about race conditions in the "queue". If I'm reading the code correctly, I think that this strategy will continue to select the same items if the rate the queue is being processed is slower than the rate this loop runs, which I believe results in the queue getting filled up with multiple copies of the same item.
Second, I am unsure if this is going to do the correct thing when a piece of content has multiple audits, some of which are failing and some of which are succeeding. Are we sure that it will only pick the ones who's most recent audit has failed? The code currently looks like it will filter out all successful audits, and then select the most recent failed one... which doesn't seem correct.
Agree with this observation. It will need to be addressed
Agree. Understanding how to effectively execute a subquery for the solution using sea-orm remains elusive to me. |
Did you find this bit in the docs? |
I did. I just haven't been able to put it together to do the sequence of things required for the strategy |
Issue addressed
Proposed changes
Adds the
SelectionStrategy::Failed
Additional info