Skip to content

KAT-3696 Log the full cause when provider event ingestion fails - #363

Draft
gannonh wants to merge 1 commit into
mainfrom
feature/kat-3696-log-the-full-cause-when-provider-event-ingestion-fails
Draft

gannonh wants to merge 1 commit into
mainfrom
feature/kat-3696-log-the-full-cause-when-provider-event-ingestion-fails

Conversation

@gannonh

@gannonh gannonh commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Fixes KAT-3696.

The orchestration V2 provider event ingestion failed warning logged cause as a Cause object, which the log formatter prints as cause: { failures: [ [Object] ] }. First turns on new threads intermittently fail with "provider event stream closed unexpectedly" on the nightly, and this log was the only place the underlying error could appear. It now logs Cause.pretty(cause).

No behavior change beyond the log field. Does not fix the intermittent failure; that needs the real cause from the next occurrence.

Verified: new test logs the rendered cause when provider event ingestion fails fails on the old code (expected 'object' to equal 'string') and passes with the change; the full RunExecutionService.test.ts passes (48 tests); tsc --noEmit reports no errors.

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@linear-code

linear-code Bot commented Oct 6, 2026

Copy link
Copy Markdown

KAT-3696

@coderabbitai

coderabbitai Bot commented Oct 6, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
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