Thanks! I just solved it, everything's cool. I'll mark this as resolved.

fixed! All tests have passed, warnings fixed also

Just completed the kata in C. It has a bunch of issues with compilation (warnings, missing includes), but it is compilable and solvable in C. stderr looks nasty tho.

Same issue here! Cannot compile and run code. Please fix.

I also get a bunch of warnings about comparing integers of different types - maybe just needs a bit of casting?

mmm, possible yes. Just note that when I said a change on version of the runner, I wasn't talking about the version chosen in the edit panel but the one of the stuff that is actually running the whole environment.

(edit: ...but that might end up in the very same behavior, yeah... :/ )

you can get those info through the "revisions" page in the edit panel.

As far as I know, only when there are changes in the desription or in the codes, not when it is a simple version change:-(

you can get those info through the "revisions" page in the edit panel. The only thing you cannot know, iirc, is who approved a transaltion.

For C I came back to my translation, edited and published.
C++ fixed.

@hobovsky, Update: don't you think it would be good to know who approves a kata and who update it?

Warnings started appearing for both C and C++ kata after tools got updated to CLang 8. I think compilation flags for warnings (-Wall?) were added for CLang 8, but they are not there for other versions of C and C++ runtimes. That's why so many kata suddenly got affected.
You might want to take a look also at oher C and C++ translations of your kata, because they may have lots of warnings now, even if there were none in the past.

PS. initial setup of C++ version does not compile (vector header is not included, type name vector is used instead of std::vector), would you consider fixing this too?

Sorry about that lots of warnings... I wrote long ago a C translation which was replaced by another one from @Uniapi and approved by somebody. I think there were no warnings when @Uniapi's translation was approved but C was updated by somebody (I don't know who approved it and who updated it).
When I have more time I will come back to my translation.
Notice that the warnings don't prevent you to pass the kata.

Hating C is natural, there's nothing to be ashamed of.

Things you see in the console are not errors, they are compilation warnings. They probably do not stop you from passing the kata, and they should not be the direct cause of your problems, but amount of them indeed does deserve dedicated issue.

Your problem is execution timeout tho, what could mean that your solution is too slow or falls into some infinite loop. Do you know what input makes you fail? You could recreate it locally and see if you have the same problem on your machine for the same array. Here is a tip how to see the input, but in C it will be a bit more complicated: you have to print it element by element and flush at the end.

If you cannot find the problem by yourself, you can share your code so we could take a look.

Ah, you are right, but I expect this to crash if z appears. Next time I'll use just [26] :). TY for let me know