-
The CosmosDB tests were disabled in PR #3815 due to timouts starting the cosmosdb emulator.
Need to evaluate *why* we're seeing timeouts and then re-enable the tests.
-
This is my current local development scenario:
- **Dotnet core 6.0** application
- **Visual Studio 2022** using a multi-container app **with Docker Compose**
- On docker-compose.yml I do the setu…
-
### Is this a bug report?
Yes
### Can you also reproduce the problem with the latest version?
Yes
### Environment
1. Dotnet version: 6.0
2. Operating system: Windows
3. IDE …
-
- Table under `Manage the emulator with command-line syntax` is outdated and missing the 4.0 option for `EnableMongoDbEndpoint`.
- Options string of `Start-CosmosDbEmulator` is completely outdated …
-
>We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the [latest SDK version](https://www.nuget.org/packages/Microsoft.Azure.Cosmos).
**Describe the …
-
>We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the [latest SDK version](https://www.nuget.org/packages/Microsoft.Azure.Cosmos).
**Describe the …
-
## Version
4.10.x.
## Describe the bug
When we refactored our tests to xUnit we moved some expensive logic to static constructors (e.g.: see [SchemaMergeTests.cs](https://github.com/microsoft/bot…
gabog updated
2 years ago
-
Integration tests should use self-contained systems (e.g. in a docker container) rather than actual cloud infrastructure.
At the moment we have tests running against Azure CosmosDB and AWS S3.
The f…
-
Hi there
I am developing a C# .NET Core app (on windows) and want to connect to the cosmos emulator running in a linux docker container on docker desktop for windows. I don't want to use SSL authenti…
-
### Description
Copied from https://github.com/Azure/azure-cosmos-dotnet-v3/issues/3010
**Describe the bug**
Using Azure DevOps and a ubuntu-latest hosted agent, when starting the container, the …
DOMZE updated
2 years ago