Repository navigation
fix(sdk-live-test): use /responses path for microsoft-foundry Responses scenarios - #5758
Open
bhaveshpatel640 wants to merge 1 commit into
Open
bhaveshpatel640 wants to merge 1 commit into
bhaveshpatel640 wants to merge 1 commit into
Conversation
…es scenarios Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
The SDK appends the request path to
{openai_endpoint}/openai/v1for Microsoft Foundry, so the harness's/v1/responsesproduced…/openai/v1/v1/responsesand every Foundry Responses scenario returned 404. Foundry now uses/responses.Test plan
microsoft-foundry/gpt-5.6-lunabaseline: 4/4 pass, includingresponses/baseline(run 40515292419); previously 404 on main (run 40513197350)Note
Low Risk
Test-harness path routing only; no production gateway or SDK behavior changes.
Overview
Fixes Microsoft Foundry Responses live tests that were hitting 404 because the harness used
/v1/responseswhile the SDK already prefixes{openai_endpoint}/openai/v1, producing a doubled…/v1/v1/responsesURL.Adds
responsesPath(model)so Foundry scenarios use/responsesand all other providers keep/v1/responses, applied to every Responses-mode scenario (baseline, features, params, modality smokes). A unit test asserts the path split formicrosoft-foundryvsopenai.Reviewed by Cursor Bugbot for commit 321e5cc. Bugbot is set up for automated code reviews on this repo. Configure here.