Development record
When no answer is recorded on the await, a concurrent invocation having already dropped it, and the run's lock is busy, takeBack still asks for the drop under the lock and its refusal says the recorded answer stays in the run's state, though there is none to drop.
issueopennitpickiss-2610142151424332
When no answer is recorded on the await, a concurrent invocation having already dropped it, and the run's lock is busy, takeBack still asks for the drop under the lock and its refusal says the recorded answer stays in the run's state, though there is none to drop.
Frontmatter
| id | iss-2610142151424332 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2610142151424332-take-back-asks-for-a-drop-not-needed.md
open on GitHub ↗ · commit history ↗