azure-search-openai-javascript
azure-search-openai-javascript copied to clipboard
Fail to run command `npm start --workspace=webapp` when using a different backend
Describe the issue:
When using a different backend according to the README , run command npm start --workspace=webapp , the error is as follows:
Repro Steps:
- Deploy this repository
- Open the alternative backend repository your want to use, for example: https://github.com/Azure-Samples/azure-search-openai-demo
- Set the frontend URL as an allowed origin with
azd env set ALLOWED_ORIGIN http://localhost:5173 - Follow the steps to deploy the Python backend.
- Once the Python backend is fully deployed, get the backend URL with
azd env get-values | grep BACKEND_URI - Set the backend URL in this repo, running
azd env set BACKEND_URI <your_backend_url> - Run
export BACKEND_URI=<your_backend_url> - Run
npm start --workspace=webapp
Environment:
- Azd version: azd version 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)
- OS: Dev Containers ,Windows and Codespaces.
Expected behavior:
Run command npm start --workspace=webapp successfully.
@jongio and @sinedied for notification.
Seems like the docs need to be updated.
Try npm run dev --workspace=webapp instead
@sinedied After using the command npm run dev --workspace=webapp instead, the current issue no longer recurs, but when chatting on the frontend page, the following error occurs:
For the second issue, the python backend has migrated to the latest AI Chat protocol using different endpoints, so it's currently not compatible. I'll create a separate issue for this.
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.
This issue was closed because it has been stalled for 7 days with no activity.
@sinedied This issue doesn't seem to be fixed, could you please reopen it?
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.
This issue seems to be unresolved, and this comment is to prevent the issue from being closed.
@jianingwang123 The issue here is due to the divergence in protocol used in the Python sample, I created #216 to track this so I'll close this one to avoid having duplicate issues