Well, it's your code that works incorrectly :P If you square negative numbers, you'll get positive ones, so it's valid data (and you need to handle it properly).

I'm not saying you're wrong in trying to "revive" the issue, but you have to be careful. I think it would be acceptable to close previous issues, if you could summarize them well in your own issue (and keeping it at the top).

I'm guessing you don't have the rights to close older issues, so you'd probably have to consult about this on CW Discord server.

At the end of the day, it should be up to the translator or the author to get this fixed, but neither seem to care too much about it, leaving us in a rough spot. And there really aren't that many active Clojure users willing to fix stuff like this :/

No, that's not how it works. You don't open the same issue twice (more than that in this case), until the old one gets resolved. You can provide the same information in older posts too.

Also, what context? You just posted some stack trace, without any context at all! (other than it's about Clojure) Much of this information was already provided in previous issues, proving this one as redundant.

Hello there. Would you be able to revise your Clojure translation, as there are multiple issues about it implying it's broken? Thanks.

There are already 2 open issues about this, including one from 7-8 years ago. Why do you think it's neccessary to raise another one?

Maybe, if you're trying it in BF.

Thank you very much for such detailed explanation!

I'm referring to the post by @pa-m, which is clearly an issue. Your mentioned post is about the Rust version. Just because it still hasn't been fixed, doesn't mean you should duplicate the issue.

You can comment on the existing one or upvote it. Even more effective method is to reply to the post that published the translation, which notifies the translator. Another option is to post about the issue on CW Discord server, and pinging the translator if they're available there.

You need to take a deeper look into your code. Right now it will always return true, because you're storing a character at some index, and then checking from beginning again so you reach the same index again, and obviously it will return true when you compare the 2.

Make use of console.log to debug your code, avoid global variables, and take a closer look at the description. "aba" should return false.

Could you please briefly elobarate on how you came up with this formula?

This issue was already raised below

It only shows up in "Past solutions" if you already hit Attempt and it was successfully passed all the tests.

However, you only need to press test/attempt button and your code will be saved locally when you enter the trainer again. If you don't, and navigate elsewhere, your code gets lost.

411 isn't the input, it's what you returned. You can print function arguments to console https://docs.codewars.com/training/troubleshooting/#print-input

If maybe you think you're doing something wrong, then maybe you shouldn't raise an issue about it, first thing. A question label is perfectly acceptable too.

The test should expect true, because none of the given answers are correct (just "B" in this case).

Not a kata issue.

You're not failing a random test, you're failing a fixed one, in particular:

strng = "12341234", arr = [ 'DIeF', 'IeFD', '12341234', '41234123', '34123412', '23412341' ]

Every rotation exists in arr, but your code returns false. There are some logical flaws in the way you're counting stuff. You should focus more on rotations of strng itself, not just arr,