Yep! Docs here: github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/deploy_features.md#using-gpt-4

Yes, here's our customization guide: github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/customization.md

Good q! Are you looking for advice on doing this in Azure PostgreSQL Flexible Server, or in PostgreSQL generally?

It depends on the SQL driver that I'm using. Django has a particular way to do token refresh, and SQLAlchemy has its own way. Django way: github.com/pamelafox/django-quiz-app/blob/main/src/quizsite/postgresql/base.py SQLALchemy way: github.com/Azure-Samples/rag-postgres-openai-python/blob/3c3d0d1d59ee4341d09e67e5f06dc38648e7ff5a/src/fastapi_app/postgres_engine.py#L37 I need to write this up in a blog post!

​@@PamelaFox in this django case how it is calling and inspecting token expiry time and calling that function ...does it is using thread or what

​@@PamelaFox please reply on both question

@@kalamkarsaurabh3 I think this article helps to explain when get_connections_params is called medium.com/django-unleashed/how-does-django-manage-db-connections-4c1a009cec91 I'm afraid I haven't found the original resource I was using when I implemented it.

HI ..can you provide flask code snippet ..where we can able to refresh token before expiry ...because getting operational error db token expired

You can have multiple indexes, but for users to select a document, I'd probably just use a field on the index, and use a AI Search filter expression to filter by the document's filename.

Hm, what's your log level set to? It's usually defaulted to WARNING for production. If youre trying to see INFO level logs, you'd need to decrease it.

@@PamelaFox Thank you for your reply. I read about this in a GitHub thread on AzureML, and this solution worked for me as well. " The issue is likely due to AzureML calling the "module level" logger during import, which creates the root logger and causes subsequent calls to logging.basicConfig to be ignored. To resolve this, you can: Run basicConfig before importing any AzureML library (e.g., any member of azureml.core). Alternatively, create a local logger with its own handler that does not propagate to the root logger created by AzureML. This is necessary if you want to change the formatting. " I tried running basicConfig before importing any Azure library and was able to see the logs in Kudu.

@@PamelaFox Thank you for your reply. I read about this in a GitHub thread on AzureML, and this solution worked for me as well. The issue is likely due to AzureML calling the "module level" logger during import, which creates the root logger and causes subsequent calls to logging.basicConfig to be ignored. To resolve this, you can: Run basicConfig before importing any AzureML library (e.g., any member of azureml.core). Alternatively, create a local logger with its own handler that does not propagate to the root logger created by AzureML. This is necessary if you want to change the formatting. I tried running basicConfig before importing any Azure library and was able to see the logs in Kudu.

@@PamelaFox Thank you for your reply. I read about this in a GitHub thread on AzureML, and this solution worked for me as well. The issue is likely due to AzureML calling the "module level" logger during import, which creates the root logger and causes subsequent calls to logging.basicConfig to be ignored. To resolve this, you can: Run basicConfig before importing any AzureML library (e.g., any member of azureml.core). Alternatively, create a local logger with its own handler that does not propagate to the root logger created by AzureML. This is necessary if you want to change the formatting. Otherwise, simply setting the logger level (e.g., logger.setLevel(logging.DEBUG)) should suffice. I tried running basicConfig before importing any Azure library and was able to see the logs in Kudu.

@@PamelaFox Thank you for your reply. `basicConfig` was not updating the level to `INFO`. I had to move it above any Azure imports to fix the issue.

See you there!

Lol thats fine, theres a fine line between teaching/learning/doing. I figure lots of folks watching wont actually be teaching, given how few teachers there are in the world!

We just use the browser's built-in PDF viewing functionality. There was a PR once that added a specific package for viewing PDFs, but it added too much bloat to our bundle.

Thanks!

I'm just finishing up some tests for it, aim to merge this week. (At Build this week in Seattle so I need to give that talk first!)

The gpt-35-turbo-instruct model does not support function calling, as far as I understand, so I'm guessing that's the error you're seeing. You can remove "tools" and "tool_choice" from the chat completion call and see if that fixes the error.

@@PamelaFox Mam how can I know the API Version of a Model Name like gpt-35-turbo through azure portal.

Aw thank you that's so kind of you to say. Glad it was helpful!

This app is structured to output a JSON API. You can see a description of the output format here: github.com/Azure-Samples/ai-chat-app-protocol The frontend sends user messages to that API, but you can send requests to it directly as well.

Hm, I'm confused as to whether you're trying to use it with OpenAI.com or Azure OpenAI? We do support both. If it's not working, please file an issue in the repo where we have better support for code sharing.