Thanks! Updated the description.

No, you're failing the second test in the "error handling" group:

it("error handling", () => {
  Test.assertEquals( encode( "abc", "x" ), null );
  Test.assertEquals( decode( "abc", [4] ), null );
  Test.assertEquals( decode( "abc", [-1,-2] ), null );
});

Not a kata issue.

An update was made by @ITSOS, should be good now.

that's because I started the translation before you modified the description. Don't worry, I'll fork and approve it myself (since I can, as a mod)

Cheers

Normally you should review it, or find someone to do so, if you don't know the language, yes. Now, considering I'm always around, you'd just have to poke at me by answering to one of my issues in the discrouse (or the suggestion ofr the transation, actually), so that I can fix any mistake I'd done.

You still should do a quick reading to see if everything seems conform to you, ofc.

Can you verify if it's ok now. Make sure to reset the kata in the editor.

That's an issue of the kata. EDIT: ok you logged an issue :) EDIT EDIT: and I fixed it ;)

I see, somehow the reference solution passes all tests. So maybe we are missing something. To be honest, I don't even understand the description of this kata. I passed by trial and error.

I don't understand what you are saying, but it does look random tests are complete BS

as Chrono said this is not a kata issue because it is not something that kata authors/contributors can act upon. if the issue persists, you can report a bug here

I see it in your completed kata's list. Either way, it's not a kata issue, because there is nothing that can be done in the kata to fix that.

thanks

fixed

This is the total time from 1 to 250. I added caching and it works now.

Our story resembles @Krillian... well, except for the fact that you really seem to have taken codewars more serious than I did. I'd really like to get to know you more if that's possible.