-
Notifications
You must be signed in to change notification settings - Fork 0
[Sprint 19] Resolve remaining database runtime issues #348
Copy link
Copy link
Closed
Labels
go:needs-researchNeeds investigationNeeds investigationsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membersquad:boromirAssigned to Boromir (DevOps / Infra)Assigned to Boromir (DevOps / Infra)squad:gimliAssigned to Gimli (Tester)Assigned to Gimli (Tester)squad:samAssigned to Sam (Backend / .NET)Assigned to Sam (Backend / .NET)
Milestone
Description
Metadata
Metadata
Assignees
Labels
go:needs-researchNeeds investigationNeeds investigationsquadSquad triage inbox — Lead will assign to a memberSquad triage inbox — Lead will assign to a membersquad:boromirAssigned to Boromir (DevOps / Infra)Assigned to Boromir (DevOps / Infra)squad:gimliAssigned to Gimli (Tester)Assigned to Gimli (Tester)squad:samAssigned to Sam (Backend / .NET)Assigned to Sam (Backend / .NET)
Database issues are still visible after PR #346/#347. Revisit the running Aspire/AppHost database path and resolve the remaining MongoDB/runtime failures.
Initial scope:
Requested by Boromir via Ralph.