Can't end odometer goal if implied end date within akrasia horizon

[dreeves]

Desiderata

• Diagnosis / explicit replicata?

---

This may be another manifestation of a bug where the server falsely rejects a new graph matrix for violating the akrasia horizon constraint. And it maybe a Beebody issue, not Beebrain.

Replicata from Nicky below, using the non-visual graph editor:

I hate the one that stops me ending an odometer goal (by changing it from total/rate to total and an end date of today) if the implied end of the goal is in the akrasia horizon! Reproducible whenever I have an odometer graph like e.g. this:

And then I try to set it like this:

Where the only change I'm making is erasing the final rate (3 in this case) and then putting in a final date of today.

It makes the goal harder by making the end total due immediately, but...

But if the implied end is outside the akrasia horizon, this always works perfectly (I use it at least a couple of times a week) and is allowed.

Cognata

• Different off-by-one error with akrasia horizon #258
• Can't extend flat spot past the akrasia horizon #232
• Graph editor can fail to warn of akrasia horizon violation #280
• 3f99f82

Verbata: spurious errors, changing the red line, graph editor,