Expose copy default transient error list by MatthiasHuygelen · Pull Request #3903 · dotnet/SqlClient

MatthiasHuygelen · 2026-01-20T10:00:25Z

Description

The default set of transient error codes is private. This seems to make it difficult to extend error codes without copy/pasting the base set from this repository. So we expose a copy.

Issues

#2342

Copilot

Pull request overview

This PR exposes the previously private default transient error list as a public property to address issue #2342, allowing consumers to extend the error code list without needing to copy/paste the base set from the repository.

Changes:

Adds a new public property DefaultTransientErrors to SqlConfigurableRetryFactory that returns a read-only copy of the default transient error list
Removes duplicated error list from test helper class RetryLogicTestHelper and migrates to use the new public API
Adds XML documentation for the new public property and documents additional error codes (64, 20, 0, -2, 207, 18456, 42108, 42109)

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/Microsoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs	Adds public `DefaultTransientErrors` property that returns a `ReadOnlyCollection<int>` copy of the private transient error list; adds missing error codes to the private list
src/Microsoft.Data.SqlClient/tests/ManualTests/SQL/RetryLogic/RetryLogicTestHelper.cs	Removes duplicated private error list and updates code to reference the new public `SqlConfigurableRetryFactory.DefaultTransientErrors` property
doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml	Adds XML documentation for the new property and documents the previously undocumented error codes

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

MatthiasHuygelen · 2026-01-20T10:07:30Z

@MatthiasHuygelen please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@dotnet-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@dotnet-policy-service agree
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@dotnet-policy-service agree company="Microsoft"
Contributor License Agreement

@dotnet-policy-service agree

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

paulmedynski · 2026-01-20T10:35:31Z

/azp run

azure-pipelines · 2026-01-20T10:35:57Z

Azure Pipelines successfully started running 2 pipeline(s).

paulmedynski

Thanks for the submission. The team will need to discuss the public API changes, and I have one implementation suggestion.

paulmedynski · 2026-01-20T10:41:47Z

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

-                };
+                    233,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
+                    64,     // A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
+                    20,     // The instance of SQL Server you attempted to connect to does not support encryption.


I'm not sure how this error (or 207 or 18456) are transient. I'll discuss with the team.

paulmedynski · 2026-01-20T10:42:35Z

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

                    997,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - Overlapped I/O operation is in progress)
-                    233     // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
-                };
+                    233,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)


These changes constitute a public API change (altering which errors we consider transient by default), so this will need some extra scrutiny.

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml

src/Microsoft.Data.SqlClient/netfx/ref/Microsoft.Data.SqlClient.cs

src/Microsoft.Data.SqlClient/netcore/ref/Microsoft.Data.SqlClient.cs

doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

paulmedynski · 2026-01-20T13:32:22Z

/azp run

azure-pipelines · 2026-01-20T13:32:47Z

Azure Pipelines successfully started running 2 pipeline(s).

paulmedynski · 2026-01-20T15:01:12Z

/azp run

azure-pipelines · 2026-01-20T15:01:42Z

Azure Pipelines successfully started running 2 pipeline(s).

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml

paulmedynski · 2026-01-22T11:58:24Z

/azp run

azure-pipelines · 2026-01-22T11:58:50Z

Azure Pipelines successfully started running 2 pipeline(s).

benrr101 · 2026-01-22T18:59:06Z

@David-Engel Since this changes our public API, could you give this a look to see if it's something we should take?

benrr101

I like it and don't see any issues - just want to get some PM approval on it before we add to our public API!

paulmedynski · 2026-01-22T20:26:47Z

#649 also discusses transient errors.

codecov · 2026-01-22T20:30:57Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.45%. Comparing base (0a1c612) to head (aba4f96).
⚠️ Report is 8 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (0a1c612) and HEAD (aba4f96). Click for more details.

HEAD has 1 upload less than BASE

Flag BASE (0a1c612) HEAD (aba4f96)

addons 1 0

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3903      +/-   ##
==========================================
- Coverage   76.66%   69.45%   -7.22%     
==========================================
  Files         269      263       -6     
  Lines       43246    66178   +22932     
==========================================
+ Hits        33156    45962   +12806     
- Misses      10090    20216   +10126

Flag	Coverage Δ
addons	`?`
netcore	`69.39% <100.00%> (-7.30%)`	⬇️
netfx	`68.65% <100.00%> (-7.61%)`	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

David-Engel · 2026-01-23T19:25:39Z

Since this changes our public API, could you give this a look to see if it's something we should take?

My main hesitancy is I don't want changes to the list to be considered breaking changes. We already have enough things that require us to major vbump. If we can expose them in a way that changes to the error list is not considered breaking, I'm all for it.

MatthiasHuygelen · 2026-01-27T06:56:05Z

@paulmedynski So how should we proceed? Are these considered breaking? I've only added the ones that were already used in the tests.

paulmedynski · 2026-01-27T11:25:21Z

Hi @MatthiasHuygelen - The team will be meeting to discuss on Thursday, and I'll post an update after that.

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

cheenamalhotra

Do not add new error codes as transient without documentation proofs.

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

paulmedynski

We have discussed these changes, and would like to back out the additions to the error code list. All of the other changes are great!

doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml

src/Microsoft.Data.SqlClient/netcore/ref/Microsoft.Data.SqlClient.cs

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

cheenamalhotra · 2026-02-03T21:59:50Z

/azp run

azure-pipelines · 2026-02-03T22:00:19Z

Azure Pipelines successfully started running 2 pipeline(s).

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Copilot · 2026-02-04T12:22:34Z

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

        /// Default known transient error numbers.
-        private static readonly HashSet<int> s_defaultTransientErrors
-            = new HashSet<int>
-                {
+        /// <include file='../../../../../../../doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml' path='docs/members[@name="SqlConfigurableRetryFactory"]/IntrinsicTransientErrors/*' />
+        public static ReadOnlyCollection<int> IntrinsicTransientErrors { get; }
+            = new(
+                [
+                    233,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
+                    997,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - Overlapped I/O operation is in progress)
                    1204,   // The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
                    1205,   // Transaction (Process ID) was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction
                    1222,   // Lock request time out period exceeded.
-                    49918,  // Cannot process request. Not enough resources to process request.
-                    49919,  // Cannot process create or update request. Too many create or update operations in progress for subscription "%ld".
-                    49920,  // Cannot process request. Too many operations in progress for subscription "%ld".
                    4060,   // Cannot open database "%.*ls" requested by the login. The login failed.
                    4221,   // Login to read-secondary failed due to long wait on 'HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING'. The replica is not available for login because row versions are missing for transactions that were in-flight when the replica was recycled. The issue can be resolved by rolling back or committing the active transactions on the primary replica. Occurrences of this condition can be minimized by avoiding long write transactions on the primary.
+                    10060,  // An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)    
+                    10928,  // Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637.
+                    10929,  // Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again later.
                    40143,  // The service has encountered an error processing your request. Please try again.
-                    40613,  // Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'.
+                    40197,  // The service has encountered an error processing your request. Please try again. Error code %d.
                    40501,  // The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d.
                    40540,  // The service has encountered an error processing your request. Please try again.
-                    40197,  // The service has encountered an error processing your request. Please try again. Error code %d.
+                    40613,  // Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'.
                    42108,  // Can not connect to the SQL pool since it is paused. Please resume the SQL pool and try again.
                    42109,  // The SQL pool is warming up. Please try again.
-                    10929,  // Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again later.
-                    10928,  // Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637.
-                    10060,  // An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
-                    997,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - Overlapped I/O operation is in progress)
-                    233     // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
-                };
+                    49918,  // Cannot process request. Not enough resources to process request.
+                    49919,  // Cannot process create or update request. Too many create or update operations in progress for subscription "%ld".
+                    49920   // Cannot process request. Too many operations in progress for subscription "%ld".
+            ]);


Changing the default transient error collection from a HashSet<int> to a ReadOnlyCollection<int> means TransientErrorsCondition now does linear Contains checks for the built-in defaults instead of hash-based lookups. To preserve the previous performance characteristics for the intrinsic default while still exposing a read-only API, consider keeping a private HashSet<int> for membership tests and exposing IntrinsicTransientErrors as a read-only view over that set (or otherwise backing the public property with a hash-based collection).

Copilot · 2026-02-04T12:22:35Z

src/Microsoft.Data.SqlClient/tests/ManualTests/SQL/RetryLogic/RetryLogicTestHelper.cs


 using System;
 using System.Collections.Generic;
+using System.Collections.ObjectModel;


System.Collections.ObjectModel is imported but not used in this file, which will generate an unnecessary using-warning. Please remove this namespace import if it is not needed.

Suggested change

using System.Collections.ObjectModel;

Copilot · 2026-02-04T12:22:35Z

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs

        /// Default known transient error numbers.
-        private static readonly HashSet<int> s_defaultTransientErrors
-            = new HashSet<int>
-                {
+        /// <include file='../../../../../../../doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml' path='docs/members[@name="SqlConfigurableRetryFactory"]/IntrinsicTransientErrors/*' />
+        public static ReadOnlyCollection<int> IntrinsicTransientErrors { get; }
+            = new(
+                [
+                    233,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
+                    997,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - Overlapped I/O operation is in progress)
                    1204,   // The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
                    1205,   // Transaction (Process ID) was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction
                    1222,   // Lock request time out period exceeded.
-                    49918,  // Cannot process request. Not enough resources to process request.
-                    49919,  // Cannot process create or update request. Too many create or update operations in progress for subscription "%ld".
-                    49920,  // Cannot process request. Too many operations in progress for subscription "%ld".
                    4060,   // Cannot open database "%.*ls" requested by the login. The login failed.
                    4221,   // Login to read-secondary failed due to long wait on 'HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING'. The replica is not available for login because row versions are missing for transactions that were in-flight when the replica was recycled. The issue can be resolved by rolling back or committing the active transactions on the primary replica. Occurrences of this condition can be minimized by avoiding long write transactions on the primary.
+                    10060,  // An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)    
+                    10928,  // Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637.
+                    10929,  // Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again later.
                    40143,  // The service has encountered an error processing your request. Please try again.
-                    40613,  // Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'.
+                    40197,  // The service has encountered an error processing your request. Please try again. Error code %d.
                    40501,  // The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d.
                    40540,  // The service has encountered an error processing your request. Please try again.
-                    40197,  // The service has encountered an error processing your request. Please try again. Error code %d.
+                    40613,  // Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'.
                    42108,  // Can not connect to the SQL pool since it is paused. Please resume the SQL pool and try again.
                    42109,  // The SQL pool is warming up. Please try again.
-                    10929,  // Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again later.
-                    10928,  // Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see http://go.microsoft.com/fwlink/?LinkId=267637.
-                    10060,  // An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
-                    997,    // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - Overlapped I/O operation is in progress)
-                    233     // A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
-                };
+                    49918,  // Cannot process request. Not enough resources to process request.
+                    49919,  // Cannot process create or update request. Too many create or update operations in progress for subscription "%ld".
+                    49920   // Cannot process request. Too many operations in progress for subscription "%ld".
+            ]);


The new public IntrinsicTransientErrors property does not appear to be directly covered by tests (for example, verifying that it matches the built-in default transient error set and that the returned collection cannot be mutated). Given that other members of SqlConfigurableRetryFactory are exercised by tests, please consider adding a focused test for this property so regressions in the intrinsic error list or its immutability are caught early.

David-Engel · 2026-02-04T17:32:50Z

@paulmedynski
IntrinsicTransientErrors sounds odd to me. To philosophical maybe? How about InitialTransientErrors?

I also considered BaselineTransientErrors, CommonTransientErrors, KnownTransientErrors, and SuggestedTransientErrors.

Open to other suggestions, too.

expose-default-transient-error-codes

110222c

MatthiasHuygelen requested a review from a team as a code owner January 20, 2026 10:00

Copilot AI review requested due to automatic review settings January 20, 2026 10:00

Copilot started reviewing on behalf of MatthiasHuygelen January 20, 2026 10:00 View session

Copilot AI reviewed Jan 20, 2026

View reviewed changes

pregress reviewed Jan 20, 2026

View reviewed changes

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs Outdated Show resolved Hide resolved

fixed comments

cdbfe53

paulmedynski self-assigned this Jan 20, 2026

paulmedynski requested changes Jan 20, 2026

View reviewed changes

paulmedynski added Public API 🆕 Issues/PRs that introduce new APIs to the driver. Approval Needed Issues/PRs that require approval from the maintainers before changes will be accepted. labels Jan 20, 2026

Fix comments

1c96948

Copilot AI review requested due to automatic review settings January 20, 2026 12:04

Copilot started reviewing on behalf of MatthiasHuygelen January 20, 2026 12:04 View session

Copilot AI reviewed Jan 20, 2026

View reviewed changes

paulmedynski linked an issue Jan 20, 2026 that may be closed by this pull request

Expose default transient SQL error codes for extensibility #2342

Open

comments

f4358f4

paulmedynski approved these changes Jan 20, 2026

View reviewed changes

paulmedynski requested changes Jan 21, 2026

View reviewed changes

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs Outdated Show resolved Hide resolved

convert to property and add missing codes from xml to implementation

6652e99

Copilot AI review requested due to automatic review settings January 22, 2026 06:54

Copilot started reviewing on behalf of MatthiasHuygelen January 22, 2026 06:54 View session

Copilot AI reviewed Jan 22, 2026

View reviewed changes

doc/snippets/Microsoft.Data.SqlClient/SqlConfigurableRetryFactory.xml Outdated Show resolved Hide resolved

typo

aba4f96

paulmedynski approved these changes Jan 22, 2026

View reviewed changes

benrr101 previously approved these changes Jan 22, 2026

View reviewed changes

cheenamalhotra reviewed Jan 29, 2026

View reviewed changes

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs Outdated Show resolved Hide resolved

cheenamalhotra requested changes Jan 29, 2026

View reviewed changes

cheenamalhotra reviewed Jan 29, 2026

View reviewed changes

...osoft.Data.SqlClient/src/Microsoft/Data/SqlClient/Reliability/SqlConfigurableRetryFactory.cs Outdated Show resolved Hide resolved

paulmedynski requested changes Feb 2, 2026

View reviewed changes

comments

400fda9

MatthiasHuygelen dismissed benrr101’s stale review via 400fda9 February 3, 2026 19:47

rename to original name

9310e65

cheenamalhotra requested review from David-Engel, benrr101, cheenamalhotra, dlevy-msft-sql and paulmedynski February 3, 2026 21:58

fix tests

2360539

Copilot AI review requested due to automatic review settings February 4, 2026 12:15

Copilot started reviewing on behalf of MatthiasHuygelen February 4, 2026 12:16 View session

Copilot AI reviewed Feb 4, 2026

View reviewed changes

Conversation

MatthiasHuygelen commented Jan 20, 2026

Description

Issues

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

MatthiasHuygelen commented Jan 20, 2026

Uh oh!

Uh oh!

paulmedynski commented Jan 20, 2026

Uh oh!

azure-pipelines bot commented Jan 20, 2026

Uh oh!

paulmedynski left a comment

Choose a reason for hiding this comment

Uh oh!

paulmedynski Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

paulmedynski Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

paulmedynski commented Jan 20, 2026

Uh oh!

azure-pipelines bot commented Jan 20, 2026

Uh oh!

paulmedynski commented Jan 20, 2026

Uh oh!

azure-pipelines bot commented Jan 20, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

paulmedynski commented Jan 22, 2026

Uh oh!

azure-pipelines bot commented Jan 22, 2026

Uh oh!

benrr101 commented Jan 22, 2026

Uh oh!

benrr101 left a comment

Choose a reason for hiding this comment

Uh oh!

paulmedynski commented Jan 22, 2026

Uh oh!

codecov bot commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

David-Engel commented Jan 23, 2026

Uh oh!

MatthiasHuygelen commented Jan 27, 2026

Uh oh!

paulmedynski commented Jan 27, 2026

Uh oh!

Uh oh!

cheenamalhotra left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

codecov bot commented Jan 22, 2026 •

edited

Loading