search

Azure-Samples / azure-search-openai-javascript

A TypeScript sample app for the Retrieval Augmented Generation pattern running on Azure, using Azure AI Search for retrieval and Azure OpenAI and LangChain large language models (LLMs) to power ChatGPT-style and Q&A experiences.
MIT License
252 stars 130 forks source link

[bug] parsing issues in frontend #166

Closed sinedied closed 2 months ago

sinedied commented 11 months ago

Sometime the parser fails at parsing some answers, for example for the question "How to contact a representative?" I get this:

image

This also occurs quite often when trying to cite sources when the backend is switched to the Python sample:

image

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
anfibiacreativa commented 10 months ago

We have reproduced and this typically happens when the LLM returns a phone number.

github-actions[bot] commented 8 months ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed.

zaccariafra commented 7 months ago

I was also facing this issue, getting a response splitted in bullets. While trying to solve the issue, I found out that disabling the "Stream chat completion responses" option somehow solves the issue. Didn't investigate more, but the issue might be related to generating the array that contains the response.

I hope it can help somehow

anfibiacreativa commented 7 months ago

I was also facing this issue, getting a response splitted in bullets. While trying to solve the issue, I found out that disabling the "Stream chat completion responses" option somehow solves the issue. Didn't investigate more, but the issue might be related to generating the array that contains the response.

I hope it can help somehow

Thank you for the context. We're evaluating moving that responsibility to the backend. Earlier when we delivered this sample, that was not possible, but we always planned to migrate the parser for performance reasons. I will reprioritize.

nmahajanoii commented 6 months ago

any update on the issue?

github-actions[bot] commented 4 months ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed.

github-actions[bot] commented 2 months ago

This issue was closed because it has been stalled for 7 days with no activity.