The problem is that in such situation when the process which was meant to disable old versions failed, it is also possible that the newest version was not changed to default. Disabling old versions usually works well when forks are merged manually, but automated updates always leave a few kata in some unfinished, not completely updated state, and it can be confusing. The newest version is sometimes not set as default, or is active for users because they visited the trainer before update and they do not realise that another version can be selected, etc.

it usually works through the editor, after making an arbitrary change, selecting an outdated version, hitting "re-publish", waiting for the compilation error, and then selecting the newest version and re-publishing again.

done.

How problematic is it really that versions other than the most recent version which is the default do not work? What do 8 or 11 do that 17 does not?

( I don't know if it's possible to make Java 8 and 11 unavailable. In other languages, making legacy versions unavailable sometimes works and sometimes does not. )

Java 8 and 11 are available, but both of them will throw error when trying to submit code. Only Java 17 works.

src/test/java/FindOddTest.java:30: error: no suitable method found for nextInt(int,int)
for (int i = random.nextInt(1, 7); i >= 0; i--) {
^
method Random.nextInt() is not applicable
(actual and formal argument lists differ in length)
method Random.nextInt(int) is not applicable
(actual and formal argument lists differ in length)
src/test/java/FindOddTest.java:31: error: no suitable method found for nextInt(int,int)
int element = random.nextInt(-100, +100 + 1);
^
method Random.nextInt() is not applicable
(actual and formal argument lists differ in length)
method Random.nextInt(int) is not applicable
(actual and formal argument lists differ in length)
src/test/java/FindOddTest.java:32: error: no suitable method found for nextInt(int,int)
int count = random.nextInt(1, 5) * 2;
^
method Random.nextInt() is not applicable
(actual and formal argument lists differ in length)
method Random.nextInt(int) is not applicable
(actual and formal argument lists differ in length)
3 errors

Wouldn't it make more sense to just make rust match the performance requirements of the other languages? I don't think this was ever intended to be a performance kata.

Rust version seems to be stricter than older languages and rejects non-O(n) solutions. To pass Rust tests, you need to make your solution performant. Arguably the same should be applied to all languages to make the challenge uniform.

So what's the kata issue? Because "your code" issues are not kata issues.

Please see https://docs.codewars.com/training/troubleshooting

And, this is in Rust?

it keeps timing out on the real tests but is fine on the sample tests..

Your solution seems to be wrong, it does not seem to return anything at all.

This bug report gives me zero idea what to fix.

Logged correct inputs but saying its not correct....

Yes, it was necessary to wait for it to mature like Parmesan cheese.

Yeah, maybe I should have waited one more year.

Thank you, that was very quick.