Yes. Maybe my for my next kata published, I may actually get on the leaderboard on authored katas.

warning: sounds good, yes (actually, expecting outputs smaller than the input is just an error in the reasonning, yes)

2dan: 5.0% left. Hence... Still some months to go, I guess x) (maybe still in 2020. 'Will mostly depend on my motivation. Which is pretty low these days... :/ )

Also, added message that shows n and k.

@Blind4Basics
Some solutions rely on the highest n can be, so maybe not. Should I just warn users that the result may be way larger than 1e6.
Btw, how far are you from 2 dan, I'm just curious;-)

The numbers tested are less than 10^6. However, the result may be larger

@tonylicoding: are those restrictions really needed? maybe just remove them, warning the user that huge numbers will be tested too? (you could add one or two of this kind of sample tests to make it clear)?

(Python)

In kata descrition there is a note:
1<n<10^6
1<k<10

I have some failing tests and this is the output of one of them:
"81514610699888 should equal 5094663168743"
Those numbers are much bigger than 10^6
Log output should be more descriptive like: for n=some value (k=val2) should equal: val3

Actually,, I forgot to edit the k. 1 < k < 10. So, k can be from 2 to 9. Had to change random tests from random.randint(1, 1e6) to random.randint(2, 1e6-1)

Added

Solve them too(but I don't think that gonna happen(because the those ranges are hard-coded)).

missing fixed test: (1152, 3) -> 12

Hi, a quick doubt.If the values of n and k are not in the given range i.e (1<n<10^6) and (1<k<8), then what should the function return?

Sorry, I copy-pasted it from the previous version :-) But thanks anyway

This is a Codewars bug that happens when a description page is loaded with TurboLinks for the first time.

KaTeX is currently only included on the description page and TurboLinks fetches it, but it seems like Markdown is rendered when it's not ready. The inline math code span is rendered as normal code span when katex is not available.
Browser refresh fixes it because it'll load all the assets before running our scripts. Navigating to another page and coming back should also fix it because KaTeX gets loaded when visiting the description page.

I'll look into it.

Added: If you see this: refresh your page

Ok, I see it now, thanks.