the issue is with how you measure whether your code is correct. by measuring differently from the tests, you get a different outcome. if you measure the same way, you will find that your function misbehaves. for example:

assert digitize(123) == [1, 2, 3]

You're printing something and returning something else. There is no issue with the kata.

I've never had to pay for using Codewars, but here's the kicker, you can try this same code out on your local machine! Just make a list with 10 million entries and have your function run over it. You can even have just the same number repeated that many times.

Sometimes the servers can be slow, but this problem expects a solution that makes even parsing 10 million results a cinch!

You can try again, I added failure messages for users who did not buy the paid subscription.

No, everyone can see failed test cases for free. Usually tests show them, but if they don't, everyone can use print to see them.

No, codewars red people don't get anything like that. You can always just print the input to see what it is.

If your solution times out, it means it does not pass all tests. It passes some tests, but not all of them, because it runs out of time.

Paid users have some additional features, but they do not get easier tests.