You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we find a team in the event feed that has a category or affiliation not yet present in DOMjudge, we try to create it here. However, we do not set any name and this gives an SQL error.
We can do two things:
Do not import the team at this point and put it as pending, wait for the group / category to show up.
Come up with a name (based in the external ID)
This happened because I could not import JSON files for the PC^2 GNY2024 shadow (since they are wrong) and they never gave us the group event. It should never happen in practice, but clearly it did.
My vote would be option 2, to make the event feed reader a bit more robust.
The text was updated successfully, but these errors were encountered:
When we find a team in the event feed that has a category or affiliation not yet present in DOMjudge, we try to create it here. However, we do not set any name and this gives an SQL error.
We can do two things:
Do not import the team at this point and put it as pending, wait for the group / category to show up.
Come up with a name (based in the external ID)
This happened because I could not import JSON files for the PC^2 GNY2024 shadow (since they are wrong) and they never gave us the group event. It should never happen in practice, but clearly it did.
My vote would be option 2, to make the event feed reader a bit more robust.
I assume we still update it when the correct event comes in?
When we find a team in the event feed that has a category or affiliation not yet present in DOMjudge, we try to create it here. However, we do not set any name and this gives an SQL error.
We can do two things:
This happened because I could not import JSON files for the PC^2 GNY2024 shadow (since they are wrong) and they never gave us the group event. It should never happen in practice, but clearly it did.
My vote would be option 2, to make the event feed reader a bit more robust.
The text was updated successfully, but these errors were encountered: