mirror of
https://github.com/getsentry/sentry-for-ai.git
synced 2026-09-14 14:28:22 +08:00
Daniel Griesser
9a86d717e8
The Flue CLI emits build progress messages ('[flue] Building:',
'[flue] Source root:', etc.) to stdout BEFORE the agent's JSON result,
not to stderr as the docs imply. The smoke script and the reusable
workflow both captured raw stdout to result.json and then ran jq on
it, which failed with 'parse error: Invalid literal at line 1, column 6'.
Fix: capture the raw output to flue-output.log, then extract the
trailing JSON object (everything from the first line starting with
'{') into result.json via 'sed -n /^{/,$p'. The raw log is now
uploaded as a separate artifact alongside result.json so we can debug
build issues post-run.
Verified locally: smoke run against getsentry/sentry-go#1302 now parses
cleanly. The agent correctly emitted a single 'skip' action recognising
that the removed ContextifyFrames integration was never user-facing
and so doesn't create drift in the sentry-go-sdk skill.
Co-Authored-By: Claude (claude-sonnet-4-6 via Pi)