Issues with validation, workaround in place

[nolan]

For the last few days, event validation has usually failed to display the buttons for releasing or submitting an event when it has no errors or warnings.

We do not think this is directly related to the SafeSport changes.

As a workaround, we have put up a version of the editing/validation code that checks for the validation having completed every 5 seconds, giving a running count of elapsed time. So far this has worked every time I’ve tried it, though my test event is taking 70 seconds to complete. If there are problems please contact mnolan@uschess.org.

[jwiewel]

@nolan

For the last few days, event validation has usually failed to display the buttons for releasing or submitting an event when it has no errors or warnings.

We do not think this is directly related to the SafeSport changes.

As a workaround, we have put up a version of the editing/validation code that checks for the validation having completed every 5 seconds, giving a running count of elapsed time. So far this has worked every time I’ve tried it, though my test event is taking 70 seconds to complete. If there are problems please contact mnolan@uschess.org.

Two days ago I went back to the submission menu and then back into the rating report at which point the release option was available.

[nolan]

Since what was happening was that the online editing form was redrawing before the database had a record of the validation being complete, anything that took 30-60 seconds probably worked, including going back to the menu and re-selecting the event.

Hitting the ‘REFRESH’ button also worked for me, but if you hit it too soon you can corrupt your event.

So, what I did was put in a loop that checked for the ‘validation complete’ log entry and kept checking for it every 5 seconds until it found it. So far I haven’t seen any reports of this hanging the validation process, but we’ll see what happens when Boyd tries to do the Middle School event tomorrow.

[jwiewel]

@nolan

Since what was happening was that the online editing form was redrawing before the database had a record of the validation being complete, anything that took 30-60 seconds probably worked, including going back to the menu and re-selecting the event.

Hitting the ‘REFRESH’ button also worked for me, but if you hit it too soon you can corrupt your event.

So, what I did was put in a loop that checked for the ‘validation complete’ log entry and kept checking for it every 5 seconds until it found it. So far I haven’t seen any reports of this hanging the validation process, but we’ll see what happens when Boyd tries to do the Middle School event tomorrow.

It will probably be Maret Thorpe (backroom chief) doing the submission, and the submission of the blitz may be able to highlight any issues earlier that the submission of the main event (allowing for you to do any needed correction while the main event is still going on).

[alaskalinuxuser]

Worked for me today! It did the count, 5, 10, 15 etc. But showed the button and went through just fine. Though my events are small.

[nolan]

I copied the ratings staff on my note about the workaround, hopefully one of them will pass that information along to Maret.

[nolan]

@jwiewel

(allowing for you to do any needed correction while the main event is still going on).

Unless the web browser times out, the workaround should work for any size event. I have considered adding a checkbox for ‘batch mode’ vs the current interactive mode where you have to wait for the validation job to complete before the screen refreshes. In batch mode it would probably go back to the menu rather than refresh the page; the submitting TD can then just wait until they get a copy of the validation report via email before going back into the editing program for the next step, whether that be revisions or release.

But considering everything will change in the next year or so as the new ratings software environment rolls out, maybe the workaround will be good enough.