Repository navigation
Improve experiment assistant validation and OpenAI compatibility - #455
Merged
Merged
Conversation
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.
Complex experiment requests could receive an invalid graph twice and surface as a provider connection failure. Preserve bounded node, port and participant diagnostics for the repair request, clarify data and loop wiring, and report invalid proposals as HTTP 422 while retaining 502 for provider failures.
Support OpenAI Chat Completions with
reasoning_effort = "none"and its current completion-token limit parameter. Existing compatible endpoints retain their request format. Update the operator configuration guide. Validation, the two-request limit and draft preservation remain unchanged.Validation: all 17 checks passed on b11a4f9, including required. Focused race checks for Studio, dispatcher configuration and authenticated assistant API passed. A direct GPT-6 Sol response to the five-pair UDP/TCP DNS comparison validated and compiled to WebAssembly; the HTTP-to-metric smoke generated the exact requested data connections. Dispatcher installation checks passed. These checks establish generation and compilation, not the correctness of every measurement inferred by the model; generated source remains reviewable before running.