Skip to content
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

revert: Reverted the changes from PR-1354 #1420

Merged
merged 1 commit into from
Oct 15, 2024
Merged

revert: Reverted the changes from PR-1354 #1420

merged 1 commit into from
Oct 15, 2024

Conversation

Prasanjeet-Microsoft
Copy link
Contributor

Purpose

  • Resolve the startup error of the admin web container after local deployment, ensuring proper functionality and stability

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Before Fix:
Screenshot 2024-10-15 144720

After Fix:
Screenshot 2024-10-15 161402

What to Check

  1. Start Docker Desktop (install it if not already installed)
  2. Open the project: Open in Dev Containers-https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/azure-samples/chat-with-your-data-solution-accelerator
  3. In the VS Code window that opens, once the project files show up (this may take several minutes), open a terminal window
  4. Run azd auth login
  5. Run azd env set AZURE_APP_SERVICE_HOSTING_MODEL code - This sets your environment to deploy code rather than rely on public containers, like the "Deploy to Azure" button.
  6. Run azd up - This will provision Azure resources and deploy the accelerator to those resources.
  • Important: Beware that the resources created by this command will incur immediate costs, primarily from the AI Search resource. These resources may accrue costs even if you interrupt the command before it is fully executed. You can run azd down or delete the resources manually to avoid unnecessary spending.
  • You will be prompted to select a subscription, and a location. That location list is based on the OpenAI model availability table and may become outdated as availability changes.
  • If you do, accidentally, chose the wrong location; you will have to ensure that you use azd down or delete the Resource Group as the deployment bases the location from this Resource Group.
  1. After the application has been successfully deployed you will see a URL printed to the console. Click that URL to interact with the application in your browser.

  2. Verify whether we can successfully launch the admin web application.

NOTE: It may take up to an hour for the application to be fully deployed. If you see a "Python Developer" welcome screen or an error page, then wait a bit and refresh the page

Copy link

Coverage

Coverage Report •
FileStmtsMissCoverMissing
TOTAL310791370% 
report-only-changed-files is enabled. No files were changed during this commit :)

Tests Skipped Failures Errors Time
301 0 💤 0 ❌ 0 🔥 51.275s ⏱️

@adamdougal adamdougal added this pull request to the merge queue Oct 15, 2024
Merged via the queue into main with commit 69d0e98 Oct 15, 2024
9 checks passed
@adamdougal adamdougal deleted the PSL-BUG-8971 branch October 15, 2024 12:47
Copy link

github-actions bot commented Nov 4, 2024

🎉 This PR is included in version 1.12.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants