8a886ddc3849e512dc559b367a3f81d04b36bdd2
The download sets its attachment headers before the read, because the body streams straight from the reader and a log is unbounded input -- buffering it to size the response would defeat the reason it streams. Nothing then cleared those headers, so a 404 for an attempt with no log went out as Content-Disposition: attachment; filename="task-1-attempt-0.log" Content-Type: application/x-ndjson A browser treats that as a download: the caller gets a .log file containing the text "no log recorded for this attempt". A stale or direct download URL is enough to trigger it. The 503 for a process with no reader had the same shape. Both error paths now clear the attachment headers before writing, so the response is an error rather than a file. The successful path is unchanged. Red first: the existing test asserted the status only, which is how this passed. It now asserts the headers are cleared on a 404 and on a 503.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%