Realized a suggestions may be marked as resolved as well. My bad. ^^

since no responce within 2 weeks marking an issue as false positive. I guess my assumption was correct...

A begging suggestion, actually it's borderline issue, or so I believe.
Please refactor explaination about that 'ambiguity' stuff
because it's not clear enough.
At least not for guys not natively fluent in English.

It must be possible to follow the line with no ambiguity
(lookahead of just one step, and never treading on the same spot twice).

this "lookahead" part makes sence only after realizing what it should mean,
usually after 'attempt' failing and digging into discource.

also that Hint:

Imagine yourself walking a path where you can only see your very next step. Can you know which step you must take, or not?

don't help with this 'ambiguity' either. It looks like it suggests to use some pathfinding method.

It should more look like:

BEWARE OF AMBIGUITIES

if after '+' corner symbol line can be proceed in more than one direction the path is considered ambiguous which means: False.
so make sure each corner is a corner, not an intersection

example

If you look carefully, you can clearly see a lot of confused warriors in discussion and also a lot of solutions which rigs 'ambiguous' part in 'not very honest' ways. I wish that explaination could help them..

From kata description:

Rules for valid lines:

...
Every line "character" found in the grid must be part of the line. If extras are found then the line is not valid.

I believe the bottom branch of that grid is classified as 'extras'

I guess it's okay to remove that while it remains on discourse for historical reasons.
I still think the kata feel less smooth than most of the rest, but still bearable, i guess...

I'm sorry, but I had no luck replicating this bug. All involved solutions just keep producing correct answer. Furthermore issue you described looks simillar to mathsisfun's, which is fixed (i hope). My humble suggestion is you've got the kata in unfixed state, and it wasn't updated after fix for some reason. If so, maybe belowmentioned 'reset' button may do the magic...

Thanks for pointing it out! Yep, the cap was faulty. Applied some fixes, and now it looks like it computes this list properly. I hope the issue is settled.

made some changes in random test generator, so now it's less volatile and should not timeout unless some really rarely weird occasion.

Fixed. Thank you! =)

thanks ^_^

in python)
'RDRRDDR' solution is missing from 1st sample and
'RRRDDRDDRDRULLLUULUUURRRDDLURRDRDDR' solution is missing from 5th sample from 'sample tests' section

if code happens to generate this solution, it gonna be rejected which is somewhat misleading ^^'

it seems zsacul's issue is also legit on Python
I suspect test code fails to generate 'fail' output in "sample tests" section for some reason

what I input:

def blox_solver(ar):
return 'RDDRRDR'

what I expect:

Time: 799ms Passed: 1 Failed: 4 Exit Code: 1
Test Results:
Example Tests:
- Test Passed
- Test Failed: Solution Invalid
- Test Failed: Solution Invalid
- Test Failed: Solution Invalid
- Test Failed: Solution Invalid

What I actually get:

Time: 799ms Passed: 1 Failed: 0 Exit Code: 1
Test Results:
Example Tests
- Test Passed

STDERR
Traceback (most recent call last):
File "main.py", line 50, in
test.expect(blox_solver(x) in example_sols[i],example_sols[i])
File "/runner/frameworks/python/cw-2.py", line 22, in expect
display('FAILED', message)
File "/runner/frameworks/python/cw-2.py", line 14, in display
type.upper(), mode.upper(), label, format_message(message)))
File "/runner/frameworks/python/cw-2.py", line 9, in format_message
return message.replace("\n", "<:LF:>")
AttributeError: 'list' object has no attribute 'replace'

unmarking issue since i can, and it seemed right ¯\(ツ)/¯

Glad you updated your solution as well! i guess issue is no more, so putting it out