Skip to content

posthog: flush telemetry before propagating a failed child's exit code#6

Open
NGHINAI wants to merge 1 commit into
codag-megalith:mainfrom
NGHINAI:fix/wrap-exit-telemetry-flush
Open

posthog: flush telemetry before propagating a failed child's exit code#6
NGHINAI wants to merge 1 commit into
codag-megalith:mainfrom
NGHINAI:fix/wrap-exit-telemetry-flush

Conversation

@NGHINAI

@NGHINAI NGHINAI commented Jun 10, 2026

Copy link
Copy Markdown

codag wrap -- <cmd> propagated a failed child's exit code with a bare os.Exit inside runWrap. That skips the cli_command_completed event and the analytics.Shutdown() flush in Execute, so the PostHog queue (5s batch interval) silently drops cli_wrap_completed and cli_command_completed for exactly the runs where the child failed — in the dashboard those runs look like the CLI hung after cli_command_invoked.

Record the exit code instead and os.Exit from Execute after the flush. Exit-code propagation is unchanged: child exit 7 still yields codag exit 7.

`codag wrap -- <cmd>` propagated a failed child's exit code with a bare
os.Exit inside runWrap. That skips the cli_command_completed event and
the analytics.Shutdown() flush in Execute, so the PostHog queue (5s
batch interval) silently drops cli_wrap_completed and
cli_command_completed for exactly the runs where the child failed — in
the dashboard those runs look like the CLI hung after
cli_command_invoked.

Record the exit code instead and os.Exit from Execute after the flush.
Exit-code propagation is unchanged: child exit 7 still yields codag
exit 7.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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