local clone cannot access the api of extension like BingSearch and AI Search
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by comparing the local clone's env.local settings with the remote clone's extension configuration, focusing on the authorization used by BingSearch and AI Search. Reproduce the unauthorized API call locally and trace the local extension entry point. Done means both search APIs work locally while chat continues to work.
Written by the indexing model from the issue text.
Description
Hi!
I have an issue that the localclone cannot access the api of AI Seach and Bing as "API is not authorized" while other function like chat is working without problem as well as the remote of the clone . I did "AdditionallyAllowedTenant=* in env.local file but nothing change .
Strangely, the setting of extension is synchronized with local's, namely, when I change the setting of the remote is relected to local's immediately.
I wisht to use the functionality of AI Search because I believe Search resource is necessary for upload the file or search the previous uploaded file because I wisht to check the customized function at localclone prior to push to the Remote.
Appreciate if somebody advise how to solve this issue.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/azurechat
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
document generation Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in microsoft/azurechat
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·