-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic Prompting #98
Merged
Merged
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
* Added scenario support for generate_solution. * Moved built in conversations into the config. They are going to be removed from code: ie. set_solution. * Added Dynamic Prompts
…stem messages: Allows for conversations to be loaded from the config file. Also added support for them in BaseChatInterface. BaseChatInterface also removed protected messages, since they are hard to maintain when adding/removing features to the class. Built in system messages were also removed since they are now fully read from the config file. Having them built in is not maintainable and never planned to keep it this way. SolutionGenerator has added partial support for scenarios. Now need to add parser in the FixCodeCommand that will select the correct scenario system message to use. UserChat has been adapted to use AIAgentConversation along with template values. All built in messages stack pushes were removed in favor of loading them from config.
Tests are not passing. Linting is not passing either. |
Closed
2 tasks
There is a bug when |
Escape messages will add escape sequences to any f-string that is not allowed.
Closed
Closed
This was
linked to
issues
Feb 8, 2024
This was
linked to
issues
Feb 8, 2024
Closed
Closed
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.
Add dynamic prompting into ESBMC-AI. Dynamic Prompting dramatically increases the performance of FCM by using a different prompt for each type of vulnerability. Dynamic Prompting can be configured in the Config by using Scenarios. Scenarios is a list in
generate_solution
.Changes
BaseChatInterface
.BaseChatInterface
also removed protected messages, since they are hard to maintain when adding/removing features to the class.FixCodeCommand
now resolves the correct scenario fromesbmc_output
, and passes the correctChatPromptSettings
to the underlying chat interface.UserChat
has been adapted to useAIAgentConversation
along with template values. All built in messages stack pushes were removed in favor of loading them from config.