The tests are not broken. I just passed both Python and Javascript versions, the tests work fine.

It is possible that the kata has been updated which has caused some old solutions to be too slow on the latest language version, but the kata is still quite possible.

rather than taking the easy and ultimately incorrect route

I suggested making a new kata, because the performance requirements were increased drastically, invalidating virtually all of the existing solutions to the previous kata. That makes this kata effectively a "performance version" of the last one, requiring satisfaction votes and rank votes to be recast, which would cast doubt on any final judgement of difficulty, as to whether votes are still skewed by the old version.

Moreover, this approach overlooks rewarding those who solved the original version of the challenge.

People not getting free points for a kata being potentially approved at a much higher rank than they solved it, is not really a high consideration when it comes to the beta process. The quality of the kata and accurate rankings are much more important.

The BF restriction could also be heavily reduced

Oh I was looking at a JS solution of yours (?) . What language is the solution you are referring to?

Approved

Your solution does not seem to ever pass, unless you had a different one when you made this issue, but without some form of reproducability we can't call this an issue.

@mauro-1 if BF_BB(11) is not very interesting, can you tell me what value you got so I can confirm my own BB searcher (also work in progress)?

All they mean is that when you wrote the description, you said that if there are no absentees, we should use the phrase "No absent digits". But when you wrote the actual tests and your solution, you used the phrase "All digits present", which doesnt match.

So either you should update the description to tell solvers to use "All digits present", or you should change your solution and all the tests to expect the phrase "No abset digits". I think changing the description is much easier.

1.Trailing spaces means a space at the end of a line, ie. after a semicolon or bracket

3.This means it is cut short and the remaining string replaced with "...". You can fix this by adding chai.config.truncateThreshold = 0; at the top of the tests (for both sample tests, and full tests)

Not an issue

Approved

Approved

Approved

These should all (besides random tests) be fixed now thanks to mjpeters' fork. (?) Please open new issues for any new problems found.