-
Notifications
You must be signed in to change notification settings - Fork 494
Issues: Azure/azure-cosmos-dotnet-v3
Microsoft.Azure.Cosmos references many out of support and vul...
#4674
opened Sep 11, 2024 by
ericstj
Open
6
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Handling unsuccessful documents upsert / delete via Bulk API
customer-reported
Issue created by a customer
needs-investigation
#4748
opened Oct 4, 2024 by
cieciurm
Microsoft.Azure.Cosmos.Spatial.Point is not compatible with UseSystemTextJsonSerializerWithOptions or System.Text.Json
bug
Something isn't working
customer-reported
Issue created by a customer
good first issue
Good for newcomers
#4744
opened Oct 2, 2024 by
quinterojose
[BUG]:CosmosNullReferenceException when hedging enabled and client called with cancelled cancellation token
customer-reported
Issue created by a customer
needs-investigation
#4737
opened Sep 30, 2024 by
anderuso
Event Source writes on 404/0
customer-reported
Issue created by a customer
needs-investigation
#4735
opened Sep 30, 2024 by
joegoldman2
PatchItemAsync is ignoring CosmosClientOptions.SerializerOptions.PropertyNamingPolicy when set to CamelCase
customer-reported
Issue created by a customer
needs-investigation
#4733
opened Sep 28, 2024 by
calloncampbell
[ClientTelemetry] Client telemetry tests are flaky
Internal team blocked
Issue blocking internal teams
needs-investigation
Telemetry
#4731
opened Sep 27, 2024 by
neildsh
Exposing Structured Debug information on the CosmosDiagnostics class
customer-reported
Issue created by a customer
needs-investigation
Binary Encoding - Add Bulk, Batch and Patch Support when Backend starts Supporting Those Operations
BinaryEncoding
binary encoding in .NET sdk
#4723
opened Sep 25, 2024 by
kundadebdatta
Binary Encoding - Add Tests and Support for End to End Validation
BinaryEncoding
binary encoding in .NET sdk
#4722
opened Sep 25, 2024 by
kundadebdatta
Binary Encoding - Add Enable/ Disable Support for Per Request Model
BinaryEncoding
binary encoding in .NET sdk
#4721
opened Sep 25, 2024 by
kundadebdatta
Binary Encoding - Introduce Object Pooling to use Memory Stream Across Serializers
BinaryEncoding
binary encoding in .NET sdk
#4720
opened Sep 25, 2024 by
kundadebdatta
Binary Encoding - Fix Existing Serialization Gaps on Newtonsoft Reader and Writer
BinaryEncoding
binary encoding in .NET sdk
#4719
opened Sep 25, 2024 by
kundadebdatta
[Internal] - Introduce Binary Encoding in .NET v3 SDK
BinaryEncoding
binary encoding in .NET sdk
#4718
opened Sep 25, 2024 by
kundadebdatta
Documentation: Adding Compute Gateway FFCF Split Handling to Engineer Documentation
auto-merge
Enables automation to merge PRs
#4717
opened Sep 25, 2024 by
philipthomas-MSFT
Error disabling analytical store in container
customer-reported
Issue created by a customer
needs-investigation
#4715
opened Sep 23, 2024 by
hesperanca
[BUG]: Handling 403:1008 for address resolution calls.
needs-investigation
#4710
opened Sep 19, 2024 by
jeet1995
Circuit breaker: Non-PPAF scenarios
needs-investigation
Selenium
#4705
opened Sep 18, 2024 by
kirankumarkolli
Binar encoding: Per request optin/out support
needs-investigation
Selenium
#4704
opened Sep 18, 2024 by
kirankumarkolli
ConnectionStateListener: support StoreClient sharing
needs-investigation
Selenium
#4702
opened Sep 18, 2024 by
kirankumarkolli
Pacakage Upgrade: Write improvements
needs-investigation
Selenium
#4701
opened Sep 18, 2024 by
kirankumarkolli
Change Feed / Processor: Add Container Resource Id to type FeedRange.
needs-investigation
#4696
opened Sep 17, 2024 by
philipthomas-MSFT
FeedIterator.ReadNextAsync blocks in v3.38.0+
customer-reported
Issue created by a customer
needs-investigation
#4695
opened Sep 16, 2024 by
tobywicks-cv
Previous Next
ProTip!
Follow long discussions with comments:>50.