I was doing katas as usual (for the record, it's this kata), and suddenly after a failed attempt the front end instantly gives me the notification you get when all tests passed, and the "Attempt" button was replaced with "Submit Final" button.
It is demonstrably a mistake of the front end, because clicking the Submit Final button doesn't work. It just gives "There was an issue submitting your final kata solution". (And there is no way to retract the button unless user code is modified.)
I couldn't replicate this instance, but I do know other very easy ways to trigger this: if a solution passes the sample tests and fails the actual tests, quickly pressing Ctrl+S (runs the sample tests) followed by Enter (runs the actual tests) when user code editor is in focus will trigger this too. So at least there is a race condition issue here.
I was doing katas as usual (for the record, it's this kata), and suddenly after a failed attempt the front end instantly gives me the notification you get when all tests passed, and the "Attempt" button was replaced with "Submit Final" button.
It is demonstrably a mistake of the front end, because clicking the Submit Final button doesn't work. It just gives "There was an issue submitting your final kata solution". (And there is no way to retract the button unless user code is modified.)
I couldn't replicate this instance, but I do know other very easy ways to trigger this: if a solution passes the sample tests and fails the actual tests, quickly pressing Ctrl+S (runs the sample tests) followed by Enter (runs the actual tests) when user code editor is in focus will trigger this too. So at least there is a race condition issue here.