fix(opencode): run transformParams middleware unconditionally for all call types#19558
Open
robinmordasiewicz wants to merge 1 commit intoanomalyco:devfrom
Open
fix(opencode): run transformParams middleware unconditionally for all call types#19558robinmordasiewicz wants to merge 1 commit intoanomalyco:devfrom
robinmordasiewicz wants to merge 1 commit intoanomalyco:devfrom
Conversation
… call types The `if (args.type === "stream")` guard meant non-stream call types skipped ProviderTransform.message() entirely — no normalizeMessages(), no applyCaching(), no tool-call ID scrubbing. The prompt shape is the same regardless of call type. Fixes anomalyco#19557
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Fixes #19557
Type of change
What does this PR do?
The
transformParamsmiddleware inllm.tswrapsProviderTransform.message()behind anif (args.type === "stream")guard. Non-stream call types skip the entire normalization pipeline —normalizeMessages(),applyCaching(), and tool-call ID scrubbing all get bypassed.The prompt shape is the same regardless of
args.type, so the guard has no purpose. This removes it so the middleware runs unconditionally. The existing TODO comment on the line suggests this was already known to be questionable.How did you verify your code works?
bun turbo typecheck)ProviderTransform.message()is called for both stream and non-stream paths by adding a temporary log and runningbun devChecklist