This comment is hidden because it contains spoiler information about the solution
I frequently wonder how long I can get away with this exact senario before I get fired.
Sometimes some of the random test cases claim to have neither a circuit or path, but in reality do actually have a path (at least that's how testing the particular graph on paper turned out for me). I tried to find a pattern, but I couldn't. It might very well be my code that's bugged here and I could totally have messed up when figuring out the graph on paper, but maybe you should have another look on the randomized tests.
Got the solution for the first problem, but having touble on the second.
It is almost like the formula is not correct in the question?
The width and height are not equal as in the description.
Well return("") took 8 - 12+ seconds.
(Frequently timed out.)
I did manage to get python to pass the test, but I had to submit like 20 times.
Done. I thought the inital solution had been changed too
Inbuilt function name is muskTunnels but function name being tested is musk_tunnels
I would advise changing inbuilt function name to match tests
don't change the name of the kata: it may cause some quirky bugs in the DB of CW.
Sweet. I'll use those tricks in the future. Thanks.
If you don't mind, I've edited the kata to pass a copy of the input to the user. I've also made it so the previous solutions haven't been invalid by the renaming of the function.
I've also used inline code blocks to format the description a bit more nicely.
May I give a suggestion - maybe change the name of the kata to something more related to the task? Less people maybe feel inclined to solve this kata because the name may not sound too interesting.
You can pass a copy of the input to the user.
How is it not 69?
Random test expect None sometimes.
arr = [1, 2, 3]
expected = internal_solution(arr)
or you pass a copy of the input, like this