Skip to content

Conversation

@nathannewyen
Copy link
Contributor

@nathannewyen nathannewyen commented Jan 16, 2026

Summary

  • Trim whitespace from text content before checking if empty
  • Filter whitespace-only messages and text parts for all providers
  • Add tests for whitespace-only content handling

Fixes #8903

@github-actions
Copy link
Contributor

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate Found

PR #7086: "fix(provider): trim whitespace and filter empty content in transformations"
#7086

This PR appears to address the same issue - filtering and trimming whitespace content across provider transformations. The current PR #8954 is likely implementing a similar or identical fix. You should:

  1. Check the state of PR fix(provider): trim whitespace and filter empty content in transformations #7086 (is it open, closed, or merged?)
  2. If it's already merged, confirm whether PR fix: filter whitespace-only content for all providers #8954 is addressing the same code or a different aspect
  3. If it's open, consider consolidating efforts or marking one as a duplicate

Apply consistent whitespace trimming across all provider transformations.
Trim text content before checking if empty, filter whitespace-only
messages and text parts for all providers.

Fixes anomalyco#8903
@nathannewyen nathannewyen force-pushed the fix/whitespace-content-validation branch from 59b8666 to cee52ce Compare January 16, 2026 19:38
@rekram1-node
Copy link
Collaborator

pretty sure glm models have a weird behavior where they do empty text that actualy has to get sent back or something I remember there being some weird bug last time I tried this

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.

Whitespace content causes API validation errors in provider transformations

2 participants