-
Notifications
You must be signed in to change notification settings - Fork 220
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
There was an issue submitting your final solution #391
Comments
Thanks for reporting. I've seen this come up in the logs a few times today. It looks like it happens for specific kata + user combinations. My theory is that a database upgrade by our hosting provider has caused the issue. The ORM we are using is in bad need of an upgrade which I am starting work on tomorrow and should have it done and tested hopefully within a few days. Right now I believe that is the best hope to resolve the issue. |
Just dropped in to confirm that I have the same issue on multiple katas, e.g.
(logged in as this GitHub user) Furthermore, I find these katas under "completed", but I can't go to the kata's solution page, because the "Solutions have been withheld" |
Have similiar issue like anter69 for most of katas, eg: https://www.codewars.com/kata/ipv4-parser/ (logged as github user) |
Have the same issue with js katas. If I'll press many times it can suddenly work, but not always. Example kata: p.s. |
If I force the SUBMIT FINAL button by pressing many times after getting the issue, sometimes I have a normally working solutions page, sometimes I switch to my solutions and see that my last solution (2nd or 1st) is not listed (If check after time they are ok). And once I had a message that the solutions are locked for me cause I haven't finished the kata yet after the SUBMIT FINAL. p.s.
|
Thanks for the details. This was an issue before the site infrastructure was changed, but it looks to have become more common after the transition. I'm working on some site updates to hopefully take care of the root issue. |
I started experiencing this issue this evening, as well. It occurs with every kata I try. I am logged as a github user. Although I suspect this may not make a difference, I am only working on JS katas. |
I have the same issue - I'm getting "There was an issue submitting your final solution" message whenever I try to submit JavaScript katas. I'm logged in a GitHub user. |
I have the same issue with python |
Yesterday I had the same issue on this kata https://www.codewars.com/kata/526a569ca578d7e6e300034e/train/javascript. Today it cannot be loaded at all. The ruby version loads, but cannot be submitted. |
I just solved a kata, it worked fine. However, when I tried to submit a new solution (somewhat different) then I got the "There was an issue submitting your final solution" error message. |
I've deployed a fix that should hopefully solve this, based off of some of the examples that I've found and tested. |
I've tested 'submit final' few minutes ago, but same error is occured again ... (submit before final is fine) test kata : https://www.codewars.com/kata/5747fcfce2fab91f43000697/train/python |
It works ( and it's really fast ) for https://www.codewars.com/kata/526a569ca578d7e6e300034e/train/javascript. Thanks. |
As far as the "possible fix deployed" tag, I'm able to log in fresh, train again on this kata: https://www.codewars.com/kata/5626b561280a42ecc50000d1, submit and submit final, and get the same error every time still. |
I still get the same error message on at least two katas. |
Just had this issue on https://www.codewars.com/kata/56269eb78ad2e4ced1000013/train/javascript while logged in as a github user. |
I'm having problems refactoring this https://www.codewars.com/kata/551f23362ff852e2ab000037/train/javascript/5763bd8b1d8b623f5c0001a7 edit: It seems that I cannot refactor any kata previously submitted. I'm logged in with email. |
Hi everyone, Same error for solutionId = 5764fea1edc6f7a9450001ca |
@jhoffner Same issue: There was an issue submitting your final solution. So, I can't submit my final solution on https://preview.codewars.com/kata/570cc83df616a85944001315/, and I don't know but Word Count is in my list of solved katas: And yet, I didn't submit any solution because I'm getting the issue. So, I don't understand why this kata is in my list of solved ones. |
Having the same issue. I passed a kata but the author decided on some changes making my solution invalid. Passed all tests again but receive "There was an issue submitting your final solution". |
The issue persists: I just completed kata 5676f07029da352ba2000065, the solution was submitted successfully -- however, when trying to submit a different solution, I get the usual error message. I would be happy to provide more details if needed, just explain where/how to extract it from the browser (chrome). |
Same here with this kata: https://www.codewars.com/kata/573c84bf0addf9568d001299. |
I've managed to reproduce this with the following steps (may not be the only cause?):
|
The issue seems to be mostly gone. Thanks! |
Final submit just worked for me. Thanks, guys! |
Awesome. Yeah it ended up being caused by a irreversible DB upgrade and a 3 year old bug in Mongoid that I tracked down and monkey patched. I'll leave this open for a bit longer just because there may be some straggler accounts that need to be repaired. |
The issue seems to be fixed. Thanks. |
Thanks for your work on this |
On the 'Argue the toss' JS Kata my solution passes all tests. However, I get this error message when trying to submit the solution. "There was an issue submitting your final solution".
function anArgument() {
var endString = ''
var firstArg = '"' + arguments[0] + '"';
if( arguments.length === 1){
return 'You gave me 1 argument and it is ' + '"' + arguments[0] + '"' + '.';
} else if ( arguments.length === 0) {
return "You didn't give me any arguments.";
} else {
for ( var i = 1; i < arguments.length; i++ ) {
if( i + 1 === arguments.length ){
endString += ' and ' +'"' + arguments[i]+ '"' + '.';
return 'You gave me ' + arguments.length + ' arguments and they are ' + firstArg + endString;
}
}
The text was updated successfully, but these errors were encountered: