Hi,

Not an issue a question. Since, if you look at the top, you'll see thousands of JS completions, so the problem is on your side, not in the test suite itself. Some definitions (terminologies specific to CW) and useful information:

• Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
• Suggestions: well, I guess that part is clear
• Question anything else that is related to you having a problem solving a kata -> that's you, currently.

Just in case, for later use... When you post issues:

• provide ALL the useful information:
  • language
  • input
  • outputs (actual expected) when relevant
  • error message when relevant
• check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
• if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)

When you post a question: well, most of the above apply too x)

When you post code, use proper github markdown, so that it's readable.

For instance, either your code is too slow and you have to change your algorithm, or you put in there a loop that never terminates in some cases.
Trick: print stuff to the console from inside the loop(s) so you'll hit the buffer limit size before the time out limit and you'll be able to get feedback about what's going on in your code.

cheers