v0.1.0 hot fixes: generated code is malformed + OpenAI version bump #32
Conversation
This file contains 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
…ng the SQL++ queries). Marking the specific variables that we know are safe (i.e., the generated code and the user query).
TJ202
approved these changes
Jan 2, 2025
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.
Using autoescape=True messed up the rendering for some tools (including the SQL++ queries). Marking the specific variables that we know are safe (i.e., the generated code and the user query).
There is a TODO in the "test_tool_generator.py" that will catch this error in the future (for the GA release).
The second hotfix pertains to a secondary dependency for our template agent (with_controlflow --> OpenAI), thus the need to bump up the controlflow version. The issue here pertains to a weird API error raised by OpenAI calls.