This isn't an issue with the tests. Your code likely isn't doing what you think it's doing. Look up operator precedence in java.

No, it doesn't bother me at all. I don't know why it bothers you so much. This is a total non-issue. There's already a better way to do what you want, you're complaining that you can't do it in a worse way.

This is an old issue, I wasn't able to find any empty it blocks in any of the translations, I'm guessing it's been fixed.

This was fixed at some point, the python tests look good now.

This was fixed at some point.

107999 would not be valid because 0 is smaller than 1, therefore the digits in 107999 are not in increasing order. This is not an issue.

This is an issue with your code. In your code, arr is a global variable, so when the code runs the second test, there are still values from the first test in arr. You must not have been running more than one test locally, otherwise you'd see the same behavior in visual stuido.

An issue is a bug with the kata. This is not a bug with the kata, it's a bug with your code. You don't return an iterable with any inputs. In the case of the first sample test, the code won't even reach your return line. For javascript, you should be returning an Array.

It's nearly impossible to change a kata's rank once it has been set. The process of doing so is disruptive and labor-intensive and for that reason, it is almost never done. Something would have to be egregiously wrong with a kata's rank to get re-ranked (like a 1-kyu rank with an 8-kyu difficulty level).

As natan said, it looks confusing, but what it's saying is that it expected [number, string, string] to be returned, but your function returned [number, number, number]

Yes... you can do that.

The length of your code has nothing to do with how efficient it is. You could write 50 lines and have a more efficient solution than the one line you have now. It just depends on how many instructions your CPU is actually performing. And right now, when n is something large like 9000000000, your solution causes the cpu to do a lot of work.

It looks like you might be overwriting the expected result in memory, there is no issue with the tests.

The elements in the input list are not guaranteed to be unique.