-
Notifications
You must be signed in to change notification settings - Fork 321
where exactly should we load secret.env file? Haizz, my memory is having some trouble, can you repeat what you just said? #137
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
Comments
Hi @james-tn do you have any update on this issue? The same obstacle is preventing us as well. |
@rcy0228 @amitlals the secrets.env should be directly under copilot directory. AZURE_OPENAI_ENDPOINT="" |
Hi @james-tn cloud please let me know which files we are using for payroll_hr and payroll_hr_cache. AZURE_SEARCH_INDEX_NAME="payroll_hr" Should these indexes be created in the search service? |
Hi @james-tn , does this code deploy the model automatically or we should deploy it manually? |
I was able to fix the issue after updating the deployment_id value with the actual OpenAI deployment name instead of self.engine but the agent is only able to reply for employee name and id not for further questions, getting the below error using faiss tried both using azcs and faiss, any idea on the same? edit: seems like the issue is with only search_knowldge function using faiss and azcs, I was able to run the queries and got the expected output. |
If you want to use Azure Cognitive Search, you need to setup index and import docVectors.json to AZURE_SEARCH_INDEX_NAME="payroll_hr". If not, just set USE_AZCS="False". |
Question, where exactly should we load secret.env file?
agent name Lucy starting agent name Jenny
agent name Paul starting agent name Jenny
agent name Jenny starting agent name Jenny
agent name Lucy starting agent name Jenny
agent name Paul starting agent name Jenny
agent name Jenny starting agent name Jenny
Exception as below, will retry
The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.
Exception as below, will retry
The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.
Exception as below, will retry
The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.
Every response says same
Haizz, my memory is having some trouble, can you repeat what you just said?
The text was updated successfully, but these errors were encountered: