| Ticket Hash: | e2fa082bea536e33a80634f4d0bf2fbb2ceeb4a6 | ||
| Title: | A run held back behind its user's other run is invisible, and stopping that run silently starts it | ||
| Status: | Open | Type: | Code_Defect |
| Severity: | Severe | Priority: | High |
| Subsystem: | Resolution: | ||
| Last Modified: |
2026-10-31 19:54:42 10.5 days ago |
Created: |
2026-10-31 19:54:42 10.5 days ago |
| Version Found In: | |||
| Description: | ||||
|
Found 2026-10-31. Run [f03ebe3a5d](/info/f03ebe3a5d), sent by ec2-user Oct 29 8:03 PM EDT, waited two days because ollama-session already had b399128942 in the node's care (docs/protocol-v1.md:315, 'nothing, until that run ends'). Nothing showed it waiting. When the maintainer stopped b399128942 (Oct 31 3:47:49 PM EDT), the node started f03ebe3a5d 13 seconds later, unannounced; the maintainer: 'Why did the new session start? I didn't start it! I only stopped the last one.'
Wanted: a held-back run is visible as waiting, behind which run, on the status page and in its thread; and a stop says what it will release. Deferred by the maintainer until the new daemon and the remote aarch64 ocx-node are up. | ||||