Repository navigation
Conversation
This branch has not been deployed
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 performance result-analysis examples use an outdated database representation:
requestis now JSON text, and decoded OpenAI responses are dictionaries. The current examples fail while attempting to unpickle the request, then fail again when JSON-decoding the response dictionary.Update both language guides and the bundled analysis script to leave the request text intact and decode only
response_messages. Preserve the server response ID when available, with the stored request ID as a fallback for empty or text responses.Validation:
create_result_table/insert_benchmark_data: dictionary, empty, and text responses (0/9 before, 9/9 after).make lint,make lint-imports, andgit diff --checkpassed.