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
Removing problems from a contest doesn't emit a delete
event
#441
Comments
We still need to look into how we can generate these delete events, because we also (first) have to generate delete events for all cascading deletes. |
Perhaps we can do this more easily when stuff is moved to Symfony? I can imagine we can hook on some event to do some magic |
Did you remove the problem during the contest? If not, then I usually delete all events and restart the event daemon. |
That is indeed what I normally do if I have access to the database. I did not with the BAPC instance (where I noticed this) and this is of course not ideal anyway :) |
This will also emit delete events when an entity gets deleted. Note that it will not yet emit cascading delete events.
This will also emit delete events when an entity gets deleted. Note that it will not yet emit cascading delete events.
This will also emit delete events when an entity gets deleted. Note that it will not yet emit cascading delete events.
This will also emit delete events when an entity gets deleted. Note that it will not yet emit cascading delete events.
When we remove problems from a contest, we do not call
eventlog
for deletion of that problem.This means that the CDS will think a lot of problems exist in the contest which actually do not.
The text was updated successfully, but these errors were encountered: