Richard Möhn

I guess this issue is not important, because Patchwork is not intended for end users.

The `scratch` case is not a bug. We're in this context: ``` Question: [$1: $3] Scratchpad: [$2: ] Subquestions: ``` First I thought that `scratch` without an argument would lead...

A variation: ``` What is your root question? > [0] Question: [$1: $3] Scratchpad: [$2: ] Subquestions: > ask [What about $1?] [Goes into endless loop.] ``` So we have...

Note that if `$3` in the example above is unlocked, it won't go into an endless loop. ``` What is your root question? > [0] Question: [$1: $3] Scratchpad: [$2:...

It also leads to failure in this case: ``` What is your root question? > [0] Question: [$1: $3] Scratchpad: [$2: ] Subquestions: > ask [1] Encountered an error with...

So you're against forbidding things like sub-questions of the form […]? In a case that detectably doesn't make sense, I would not let the system run until it's out of...

I see. And I just realized that patching specific cases won't cut it anyway, because they keep turning up, seemingly every time I think that I can finish the PR...

In case you're curious about the Hypothesis test: https://github.com/rmoehn/patchwork/blob/test-hypothesis-2/tests/test_randomly.py

`Context.is_own_ancestor` doesn't prevent some endless loops from happening, because there is a discrepancy between it and the memoizer. The memoizer determines only from the string representation of a context c...

We assume that H takes the same action B whenever she sees a context A. The purpose of the memoizer is to save H's work by learning H's context-to-action mapping....