Skip to content

Read gzip-compressed App output - #15

Merged
cleemansen merged 2 commits into
mainfrom
feature/gzip-aware-pickle-read
Jul 30, 2026
Merged

cleemansen merged 2 commits into
mainfrom
feature/gzip-aware-pickle-read

Conversation

@cleemansen

Copy link
Copy Markdown
Contributor

Python SDK v3 writes App output as a gzip-compressed pickle. MoveApps hands the
cargo-agent an extension-less path (/tmp/output_file), so pandas cannot infer
the compression from the file name — it is determined from the first two bytes
instead.

Uncompressed output stays readable: Apps built against an earlier SDK keep
writing plain pickles, and their stored output can still reach the agent.

Without this change the read raises, the event handler falls back to the void
analyzer as designed, and every Python App would report empty statistics rather
than an error.

Release as v2.2.0 — the agent only gains an ability, nothing breaks.

cleemansen and others added 2 commits July 30, 2026 11:56
MoveApps hands the cargo-agent a path without a file extension, so pandas
cannot infer the compression from the file name. Determine it from the first
two bytes and pass it to pandas explicitly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Apps on Python SDK v3 write their output gzip-compressed. Without this the
analysis raises, the event handler falls back to the void analyzer, and every
Python App reports empty statistics instead of an error.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@cleemansen
cleemansen force-pushed the feature/gzip-aware-pickle-read branch from 6b1b3ed to 15fc353 Compare July 30, 2026 09:58
@cleemansen cleemansen self-assigned this Jul 30, 2026
@cleemansen
cleemansen merged commit aaa26a4 into main Jul 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant