microsoft / microsoft/aspire-samples
[WebToolsE2E][Aspire] After successfully deploying the Aspire-Samples/DatabaseContainers solution, going to /todos displays the error: "An error occurred while processing your request, status: 500."
Open
Nobody has claimed this yet.
area-deployment
area-samples
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 345
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 30
Description
REGRESSION INFO: Blocked by bug #2445 on Aspire 8.0.0-preview.3.24105.21
INSTALL STEPS
- Clean machine: Win11 x64 23h2 ENU
- Install VS 17.10 Preview 2 [ Includes Aspire 8.0.0-preview.4.24129.7 ]
- Apply NuGet dotnet-tools Feeds
- Install Docker Desktop for Windows
- Install azd [1.7.0-beta.1-daily]
REPRO STEPS
- Clone aspire-samples repo from main branch
- Checkout the
preview.4branch - Open samples\DatabaseContainers.sln ( Bug 1985774 will be encountered after opening)
- Build solution
- Deploy using azd
- Open the solution folder in a Command Prompt
- Runing 'azd init', select 'Use code in the current directory' > Confirm and continue initializing my app, type a new environment name, press enter
- Running 'azd up'
- Click on the deployed 'apiservice' endpoint, then go to /todos
ACTUAL:
Note:
- Do F5 then click on the endpoint of 'apiservice' and go to /todos occasionally reproduces this issue, but refreshing the page works fine.
EXPECTED
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the failure from samples\DatabaseContainers.sln after deployment with azd, then inspect the deployed apiservice endpoint at /todos. Confirm whether the 500 persists after refresh and trace the request failure; done means /todos consistently displays the expected todos response without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, docker
- Domain
- backend, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100