Skip to content

fix: add fallback for empty response content#8

Open
michaelansel wants to merge 1 commit intoRichardAtCT:mainfrom
michaelansel:fix/empty-response-fallback
Open

fix: add fallback for empty response content#8
michaelansel wants to merge 1 commit intoRichardAtCT:mainfrom
michaelansel:fix/empty-response-fallback

Conversation

@michaelansel
Copy link

Subprocess execution sometimes succeeds but result.get("result") returns empty string, causing "Message text is empty" errors. Response content exists in assistant message stream.

Changes:

  • Collect all assistant text messages during parsing
  • Use last assistant text as fallback when result is empty
  • Add debug logging for fallback usage

Fixes "Message text is empty" error when subprocess completes successfully but result field is empty.

Subprocess execution sometimes succeeds but result.get("result") returns
empty string, causing "Message text is empty" errors. Response content
exists in assistant message stream.

Changes:
- Collect all assistant text messages during parsing
- Use last assistant text as fallback when result is empty
- Add debug logging for fallback usage

Fixes "Message text is empty" error when subprocess completes successfully
but result field is empty.
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