Inbox answer validation isn't atomic with resolving the question
This commit is contained in:
@@ -1,7 +1,5 @@
|
||||
# Bugs
|
||||
|
||||
- Inbox answer validation isn't atomic with resolving the question
|
||||
`CheckResponse` reads open state outside the write transaction and `Respond` updates by id alone (`internal/agents/respond.go:26–34`, `:93`; `internal/store/inbox.go:140`), so two concurrent answers both land, or a withdrawal is overwritten. Condition the update on `state='open'`, check RowsAffected, roll back the batch on conflict and return 409.
|
||||
- A malformed file image URL breaks transcript rendering
|
||||
`decodeURI` throws on e.g. `file:///tmp/100%.png` (`web/src/markdown.ts:347`), and `renderAll` appends events before mounting the composer (`web/src/task.ts:608–609`), so the rest of the transcript and the composer don't render. Catch the decode error and render the plain fallback link.
|
||||
- operations.md describes two incompatible event-stream designs
|
||||
|
||||
Reference in New Issue
Block a user