-
Notifications
You must be signed in to change notification settings - Fork 76
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
Implementing personalization with Gorilla #56
Conversation
e9f3ca4
to
8e64981
Compare
Given the large scope of this PR, and the fact that we need to update the backend, I'd think we should merge #46 potentially before this. |
utils.py
Outdated
@@ -0,0 +1,77 @@ | |||
import os | |||
from presidio_analyzer import AnalyzerEngine, PatternRecognizer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't you also need to include this in the requirements presidio_analyzer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where would I access the file for this?
Personalization with Bash history
Leveraging the synthesis of user's bash history to see if we can personalize the responses from Gorilla. We also use Microsoft Presidio to anonymize their bash history as well just in case. This is to prevent the model from processing a user's private information. An example synthesis of bash history looks like:
"The user appears to be working with Python and AWS. They have used pip to install several Python packages, specifically 'presidio_analyzer' and 'presidio_anonymizer'. They have also used python commands to execute URLs. Most notably for the context of the query, user ran 'gorilla' commands relating to AWS, such as listing all files in the current directory, moving a file from one bucket to another, and listing all AWS instances. Finally, they executed an 'export' command possibly setting an AWS location. The user is now interested in their AWS history. This context suggests that the user may be doing some data analysis on AWS and wants to retrace their steps or review their activities on AWS."