Skip to content

Quarantine intermittent pool worker-start timing test - #5105

Merged
mdaigle merged 1 commit into
mainfrom
dev/mdaigle/sqlclient-flaky-quarantine-1118
Nov 18, 2026
Merged

mdaigle merged 1 commit into
mainfrom
dev/mdaigle/sqlclient-flaky-quarantine-1118

Conversation

@mdaigle

@mdaigle mdaigle commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

🤖 This pull request was created by a fully automated workflow.

Description

Quarantine Microsoft.Data.SqlClient.ManualTesting.Tests.ConnectionPoolTest.MaxPoolWaitForConnectionTest with a method-level [Trait("category", "flaky")] and an observed-error comment. This affects all four non-Synapse TCP cases: MARS false/true × usePoolV2 false/true, on net462 and net10.0. Test bodies, existing categories, APIs and pipelines are unchanged.

Observation CI-SqlClient result Main revision Observed UTC
Failed, pool V2 true: expected Running, actual WaitingToRun 193066 / 3734166 / 103318, child 2 083570c61341 2026-11-18 01:48:07.438–01:48:08.528
Failed, pool V2 false: same assertion 193066 / 3734166 / 103320, child 2 083570c61341 2026-11-18 01:48:08.501–01:48:09.573
Passed, both pool versions and both MARS cases, separate job 193040 / 3733831 / 102353, 102355, all four children 083570c61341 2026-11-17 23:57:49.205–23:57:50.669

Both jobs use Windows 11 x64, net10.0 managed SNI, Azure SQL, Release/Project, Set 3, attempt 1 and image 56.0.0; allocations/times differ. The test assumes a queued worker starts within five 200-ms sleeps, then asserts its scheduler state without a readiness handshake. The observed failure is that test-specific deadline, not a SQL connection timeout. All four inputs share it.

Truncated CI names do not identify which MARS variant failed; the separate passing job covers the entire four-case population. No per-MARS failure attribution is claimed. Release-branch qualification remains incomplete; no hotfix label/backport requested. Fixes and probation are outside scope.

Issues

Historical #1465 adjusted this same worker-start wait. Open #5095 and #5073 quarantine different tests; #5094 repairs a different already-quarantined test. Complete collapsed evidence and run record, including exact case limitations, validation and checkpoint status.

Testing

Both target frameworks build; quarantine discovery selects this theory and ordinary discovery excludes it while retaining three sibling theories. Local data-provider initialization prevents individual-case enumeration. net462 focused execution failed before exercising the test (Northwind login failure); net10.0 skipped because configuration is missing. No local passing/stability coverage is claimed.

$p = 'src\Microsoft.Data.SqlClient\tests\ManualTests\Microsoft.Data.SqlClient.ManualTests.csproj'
$n = 'FullyQualifiedName=Microsoft.Data.SqlClient.ManualTesting.Tests.ConnectionPoolTest.MaxPoolWaitForConnectionTest'
foreach ($f in 'net462', 'net10.0') {
    dotnet test $p -f $f --no-build --no-restore --list-tests --filter "$n&category=flaky" -v:q
    dotnet test $p -f $f --no-build --no-restore --list-tests --filter 'FullyQualifiedName~Microsoft.Data.SqlClient.ManualTesting.Tests.ConnectionPoolTest.&category!=failing&category!=flaky&category!=interactive' -v:q
}

Result: one quarantined theory selected per framework; ordinary discovery retains three siblings and excludes this method. git diff --check and git diff HEAD^ HEAD --check passed. The linked record retains build/execution commands, initial missing-assets error and restore result.

The 518-build inventory covers 2026-11-04T14:02:42.087Z–2026-11-18T14:02:42.087Z; two run inventories reconcile 12,830 top-level results. Broader per-test discovery is incomplete after a build-wide MCP transport failure. Checkpoint not advanced.

Guidelines

Please review the contribution guidelines before submitting a pull request:

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@mdaigle
mdaigle requested a review from a team as a code owner November 18, 2026 14:20
Copilot AI balanced review requested due to automatic review settings November 18, 2026 14:20
@github-project-automation github-project-automation Bot moved this to To triage in SqlClient Board Nov 18, 2026
@mdaigle mdaigle added the Area\Tests Issues that are targeted to tests or test projects label Nov 18, 2026
@mdaigle mdaigle added this to the 8.1.0-preview1 milestone Nov 18, 2026
@mdaigle

mdaigle commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor Author
Quarantine evidence, validation and incomplete discovery checkpoint - 2026-11-18

Category-only scope and exact identity

Quarantine the method
Microsoft.Data.SqlClient.ManualTesting.Tests.ConnectionPoolTest.MaxPoolWaitForConnectionTest(string connectionString, bool usePoolV2).
Commit eadfd18d8c56167c92d3999bddb89fc9d680ad26 adds only:

// Assert.Equal: expected Running, actual WaitingToRun after the worker-start wait.
[Trait("category", "flaky")]

Its body, conditional attribute, data provider, class-level Set=3, other categories,
product code and pipelines are unchanged. No fixes, retries, probation or category removals.
The existing provider supplies the TCP configuration with MARS false/true, crossed with
usePoolV2=false/true: four cases when the target is not Synapse, two otherwise.
The method-level category intentionally affects that whole population on net462 and net10.0,
not sibling methods.

The decisive CI population is Azure SQL, not Synapse:

Fully qualified method above: semantic inputs Passing control Failing observation
Azure TCP, MARS=false, usePoolV2=false Included in the two verified passing children of 102355 One MARS variant fails in 103320; exact variant unavailable
Azure TCP, MARS=true, usePoolV2=false Included in the two verified passing children of 102355 Same limitation; do not infer child ordinal is MARS value
Azure TCP, MARS=false, usePoolV2=true Included in the two verified passing children of 102353 One MARS variant fails in 103318; exact variant unavailable
Azure TCP, MARS=true, usePoolV2=true Included in the two verified passing children of 102353 Same limitation; do not infer child ordinal is MARS value

Azure DevOps truncates connection-string display names before the MARS setting.
The exact stored names end with
(connectionString: "Data Source=adotest.database.windows.net;Initial C"···, usePoolV2: False)
or the corresponding True. Never equate the two MARS cases by that display name.
IDs below, including child IDs, distinguish observations within the service.
This is a method-level intermittency decision: the separate passing job ran the entire
fixed four-case population once and every child passed, so it covers either possible
failing MARS variant. No particular MARS variant is claimed to be the failing one.
All four inputs share the same unsupported worker-start timing assertion.

Verified failures and separate passing controls

Both builds are CI-SqlClient definition 1879, refs/heads/main, exact SHA
083570c61341c024edcea80856e72d7911ae8312.
Single-result REST responses independently matched discovery's build/run/result/outcome.
All subResults were read recursively, not inferred from grouped parents.

Observation Build / run / result / child Observed UTC start - completion
Failed, usePoolV2=true 193066 / 3734166 / 103318, child 2 2026-11-18T01:48:07.437873Z - 01:48:08.5275155Z
Failed, usePoolV2=false 193066 / 3734166 / 103320, child 2 2026-11-18T01:48:08.5012657Z - 01:48:09.5725136Z
Passed, usePoolV2=true, both MARS cases 193040 / 3733831 / 102353, children 1 and 2 child 1: 2026-11-17T23:57:49.9017001Z - 23:57:50.5982996Z; child 2: 23:57:50.414069Z - 23:57:50.6694441Z
Passed, usePoolV2=false, both MARS cases 193040 / 3733831 / 102355, children 1 and 2 child 1: 2026-11-17T23:57:50.1585692Z - 23:57:50.4156176Z; child 2: 23:57:49.2046269Z - 23:57:49.4629006Z

Both failed children report exactly Assert.Equal() Failure: Values differ,
Expected: Running, Actual: WaitingToRun, at ConnectionPoolTest.cs:265.
Their sibling children pass, but those mixed parent outcomes are NOT the passing control.
The separate 193040 job is the control, not a successful retry.
Stored parent/child timestamps occasionally disagree; the service's observed fields
are preserved instead of silently rewritten.

Test-specific eligibility and configuration comparison

The unchanged source schedules a Task.Factory.StartNew worker, sleeps up to
five times for 200 ms, then requires waitTask.Status == TaskStatus.Running.
It does not synchronize worker readiness. A correctly queued worker can still be
WaitingToRun after that arbitrary approximately one-second scheduler budget.
The failure occurs before releasing the held connection, not in a SQL
connection timeout, DNS lookup, pre-login exchange or an assertion about pool behavior.
Agent pressure may expose the weakness, but the unsupported worker-start deadline
is test-specific. This supports quarantine, not a complete root-cause diagnosis
or a stability/repair claim.

The held connection has already opened when this assertion fails.
The ordinary task's initial attempt passed 886 tests and failed the separate
MarsConcurrencyTest; its next attempt produced these two worker-state assertions.
The other run passed all 887 ordinary cases, with 88 skipped in each initial task.
No general server outage better explains a worker that has not started running.
Historical #1465 increased this
same sleep to address intermittent pipeline failures; it is context, not a current
passing control or authorization to implement another timing change.

Both decisive runs identify stage win11_Azure_Sql, phase
net10_0_AnyCPU_ManagedSNI_3, job __default, stage/phase/job attempt 1.
Configuration is Windows 11 x64, net10.0 managed SNI, Azure SQL, Release,
Project references, Set 3, Standard_D2a_v4, ADO-CI-Win11 image 56.0.0, westus2.
Different agent allocations/times and generated CI package suffixes are the
meaningful differences; source revision, image, target and selection match.
This is not evidence against a verified local SQL Server.

The ConnectionPoolTest.cs blob is unchanged between the decisive SHA and upstream
main 0a46e011d4aa8eee985fea1c298300c7e24e19ba:
git hash-object of both retrieved source texts is
960489c714066b5e69eb90c18c1ee2f122043a19.

Job mapping, logs and retrieval limitations

Both timelines have the unique job identifier
Win11_Azure_Sql.net10_0_AnyCPU_ManagedSNI_3.__default,
job ID 1599937a-74da-5c18-7c9a-92d9034abbc4,
parent phase 27dc93eb-4957-5b02-236f-894c994ee61c,
parent stage b741d4c7-06c8-53e8-475a-a9e126506e4a, attempt 1.
Run metadata independently identifies that stage/phase/job and build/definition.
Children were mapped by parentId, not by an ambiguous job-name-only match.

  • 193066 ordinary task:
    authenticated MCP log 4508, lines 1-450. Initial 886 passed / 1 failed / 88 skipped;
    task retry 1 then reports the two exact pool worker-state failures.
  • 193040 ordinary task:
    MCP log 4435, lines 1-350; 887 passed / 0 failed / 88 skipped, no task retry.
  • 193040 result publisher:
    MCP log 4500, lines 1-85, independently identifies run 3733831 and 5,450 results.
  • Initialization logs: 193066/2716 lines 1-85 and 193040/2863 lines 1-18,
    establishing matching agent image/SKU and different allocations.
  • Effective ordinary filter:
    ((category!=failing&category!=flaky&category!=interactive)&category!=signed)&(Set=3).
    The distinct quarantine task is 7b5f34e4-4c3b-55c2-50bd-394ffa5ef9c0;
    the decisive test observations are from ordinary execution.

The build-wide 193040 Passed helper failed with
MCP server 'azure-devops': MCP request failed: Transport closed.
Mapped authenticated publisher discovery and authenticated per-run pagination
returned the full control run, independently of that failure.
Build artifact listing mapped
net10.0WinAz1599937a-74da-5c18-7c9a-92d9034abbc4 to the failing job
(reported size 42,064,239 bytes). Its MCP download returned no content;
no artifact contents or additional untruncated arguments are claimed.
No alternate artifact REST endpoints or credentials were used.

Supplemental public REST reads were limited to the permitted individual run,
single-result-with-SubResults, and build timeline endpoints.
Responses required HTTP 200, JSON, matching run/result identities and expected fields.
Requests were sequential, cached within this session, with finite transient retries.
Discovery and result-list pagination remained authenticated MCP.

Inspected interval, reconciliation and unfinished coverage

No complete tagging checkpoint exists in the live prior records read:
#4980 and
#4996 are merged;
#5073 and
#5095 are open.
Fix/probation records do not advance discovery.
The inspected completed-build finish-time window is exactly
2026-11-04T14:02:42.087Z through 2026-11-18T14:02:42.087Z.

Authenticated MCP rechecked all seven specified definition names/IDs as Enabled.
sqlclient-ci-stress 2250 was verified Disabled and excluded.
Six bounded build pages (50, 100, 100, 100, 100, 68) returned
518 unique completed builds; the last continuation token was empty.
No branch or result filter omitted release, successful, partial-success or canceled builds.

Definition Succeeded Partially succeeded Failed Canceled Total
CI-SqlClient 1879 1 37 82 6 126
CI-SqlClient-Package 1917 0 25 44 7 76
PR-SqlClient-Project 2197 0 56 30 0 86
PR-SqlClient-Package 2198 0 13 9 0 22
sqlclient-pr 2281 138 0 39 3 180
sqlclient-ci-package 2300 27 0 1 0 28
sqlclient-ci-unit 2309 0 0 0 0 0

CI-SqlClient includes main 45, release/6.1 8, release/7.0 12,
release/7.1 23, release/8.0 18, and 20 other source refs.
Actual release refs were additionally verified through upstream ls-remote.
Build enumeration is NOT per-test coverage.

Authenticated build-helper failure discovery completed for main builds
193040, 193066, 193108; release/6.1 build 192610;
release/7.0 build 192218; release/7.1 build 193173;
release/8.0 build 193032.
This is not exhaustive failure discovery across the 518 builds.
Whole-window per-test review remains unfinished on main and every discovered
release branch, and on PR/development refs and successful/canceled builds.

Two relevant run inventories were completely paginated in bounded 1,000-result
pages and reconciled by unique result ID/outcome to server statistics:

Build / run Unique top-level results Passed Failed NotExecuted
193066 / 3734166 7,380 7,083 3 294
193040 / 3733831 5,450 5,332 0 118

Both Completed runs report incompleteTests=0. Passed statistics retain and SUM
the duplicate metadata entries: 7,081+2 flaky and 5,330+2 flaky respectively.
They are not overwritten or treated as additional failures.
The 12,830 top-level records are run-specific coverage, not all-build coverage.
Skipped, aborted, missing, expired and inaccessible results never count as passes.
Individual decisive grouped results were additionally verified with all children.

Checkpoint NOT ADVANCED. Next discovery must rescan its full 14-day window,
deduplicating against upstream code/PR records, unless a later complete tagging
record establishes a trustworthy checkpoint.

Other candidates, deduplication and release routing

  • MarsConcurrencyTest remains covered by open
    #5095.
    Existing split-packet proposal
    #5073 affects another Fact.
    Neither was modified.
  • #5094 is a different,
    already-quarantined shared-transaction worker-starvation repair/probation
    proposal. Read for deduplication only, not a discovery checkpoint.
    #5087 covers release/7.1
    simulator backport context. No equivalent open pool-start quarantine found.
  • DiagnosticTest.ConnectionOpenAsyncTest is unconfirmed:
    verified 193066 / 3734069 / 102236,
    2026-11-18T01:33:52.157Z-01:33:52.163Z, main SHA above,
    Win22_Sql19/net462/Set 3 attempt 1, reports missing
    Microsoft.Data.SqlClient.WriteConnectionOpenAfter. Source uses a local TDS
    simulator, but no concrete test-design weakness or comparable verified passing
    control was established. No tag and no product-defect conclusion.
  • Main ApiShould.TestEnclaveExecutionApis async grouped failures are unconfirmed:
    truncated configurations and mixed/repeated outcomes require more investigation.
    No tag for an assumed timeout or possible deterministic XML/product issue.
  • MetricsTest.ReclaimedConnections_BalanceSoftConnectionCounters,
    SqlSchemaInfoTest.TestGetSchemaAsync, WeakRefTestYukonSpecific.TestReaderMars,
    MarsSessionPoolingTest.ExecuteReader_DisposeCommand and ExecuteReader_NoCloses
    are already quarantined on main. Their new failures cause no category removal,
    probation change or duplicate proposal.
  • Release/7.0 diagnostic failures include assembly-load failures, not the main
    missing-event symptom; simulator assertions may be deterministic branch/product
    differences. Release/7.1 shows DTC-global-setting, TVP assertion and transaction
    cleanup failures; release/6.1 has XEvents timeouts and simulator failures.
    These are unconfirmed, not automatically intermittent defective tests.
    Generic connectivity/timeouts and successful retries are insufficient.
    If later evidence isolates transient setup/connectivity, the separate
    fixes/probation automation may consider bounded retries around that setup only,
    never around assertions or the behavior under test. No retry is implemented here.

No release branch qualifies for this new quarantine yet.
The sampled release builds do not establish this pool-start symptom's
within-branch failure/pass pair. No main pass substitutes for a release pass.
No Hotfix label/backport request is made and no manual backport is opened.
Release/6.1, /7.0, /7.1 and /8.0 each retain unfinished per-test coverage.
Live labels and the hotfix workflow/extractor were inspected; label availability
alone does not establish a current patch target or justify whole-PR routing.
No existing labels or human routing choices were removed.

Local category validation and execution limitations

Repository build.proj ordinary selection excludes flaky; existing quarantine
steps select category=flaky, disable coverage and use continueOnError.
No pipelines or filter infrastructure changed.

Exact commands, run from this automation's isolated worktree:

$p = 'src\Microsoft.Data.SqlClient\tests\ManualTests\Microsoft.Data.SqlClient.ManualTests.csproj'
$n = 'FullyQualifiedName=Microsoft.Data.SqlClient.ManualTesting.Tests.ConnectionPoolTest.MaxPoolWaitForConnectionTest'
dotnet test $p -f net10.0 --no-restore --list-tests --filter "$n&category=flaky" -v:q
dotnet restore $p -v:q
dotnet test $p -f net10.0 --no-restore --list-tests --filter "$n&category=flaky" -v:q
dotnet build $p -f net462 --no-restore -v:q
foreach ($f in 'net462', 'net10.0') {
    dotnet test $p -f $f --no-build --no-restore --list-tests --filter "$n&category=flaky" -v:q
    dotnet test $p -f $f --no-build --no-restore --list-tests --filter 'FullyQualifiedName~Microsoft.Data.SqlClient.ManualTesting.Tests.ConnectionPoolTest.&category!=failing&category!=flaky&category!=interactive' -v:q
    dotnet test $p -f $f --no-build --no-restore --filter "$n&category=flaky" --logger 'console;verbosity=normal'
}
git diff --check
git diff HEAD^ HEAD --check
  • Initial net10.0 no-restore discovery failed NETSDK1004 (missing project.assets.json).
    Explicit restore then passed; net10.0 build/discovery passed afterward.
  • net462 build passed with zero warnings and zero errors.
  • Both-framework quarantine discovery selected exactly this one theory.
    Ordinary class discovery excluded it and retained AccessTokenConnectionPoolingTest,
    ClearAllPoolsTest and ReclaimEmancipatedOnOpenTest.
  • Local case enumeration is incomplete: discovery fell back to the single theory
    because the SQL-backed provider could not initialize. Four-case CI population
    coverage above is not a claim of four locally discovered/executed cases.
  • net462 focused execution: 0 passed, 1 failed, 0 skipped, database login error
    Cannot open database "Northwind" requested by the login. The login failed.
    It does not reproduce the CI worker-state assertion.
  • net10.0 focused execution: 0 passed, 0 failed, 1 skipped, missing test
    configuration (FileNotFoundException, surfaced through TargetInvocationException).
    This is not passing or stability coverage.
  • Both git whitespace checks passed. The entire committed diff is two added lines.
    No user configuration, credentials or primary checkout was modified.

The loop presents the equivalent per-framework commands compactly; net10.0 commands
were completed separately after the net462 nonzero exit stopped the initial batch.
The final normal-verbosity net462 attempt reproduced its environmental error.
Local environmental failures are not concealed, repaired, or used to justify quarantine.

Publication target and boundaries

Fresh upstream main resolves SqlClientNextVersion to 8.1.0-preview1,
existing OPEN milestone #108. The one-time exclusion of 8.0.0-preview1/#101
does not apply. This PR requires Area\Tests and milestone 8.1.0-preview1;
live assignment and the exact automated disclosure first line were verified after creation.
No hotfix routing is claimed.

Published #5105, open and unmerged:
both source and target repositories are dotnet/SqlClient, source branch
dev/mdaigle/sqlclient-flaky-quarantine-1118, target main, exact head
eadfd18d8c56167c92d3999bddb89fc9d680ad26.
Live GitHub metadata confirms Area\Tests, milestone 8.1.0-preview1/#108,
the required visible disclosure first line and auto_merge=null.
Live file metadata confirms one file, two additions and zero deletions,
with the observed-error comment immediately above the new flaky attribute.
Exactly one collapsed evidence comment for this originating session is linked
from the description. The worktree is clean after commit/push.

The complete build inventory is established, but broader per-test discovery and
release qualification remain incomplete, with checkpoint not advanced.
Fixes and all probation lifecycle work are outside this automation's scope.
No builds were queued, pipeline definitions changed, automation configured,
PRs merged/approved, auto-merge enabled or accounts/repositories switched.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues were identified for the change quarantining the intermittently failing connection-pool test.

No open issues 🎉

What changed in this PR

Quarantines MaxPoolWaitForConnectionTest following intermittent worker-start timing failures, without changing test logic or SqlClient behavior.

Changes:

  • Adds a method-level flaky category covering all four MARS/pool-version cases on both target frameworks.
  • Adds a comment recording the observed Running versus WaitingToRun assertion failure.
File Description
src/​Microsoft.Data.SqlClient/​tests/​ManualTests/​SQL/​ConnectionPoolTest/​ConnectionPoolTest.cs Marks the theory as flaky and documents the observed failure; test bodies and existing categories remain unchanged.

Review effort: Balanced

@codecov

codecov Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.41%. Comparing base (17bef7b) to head (eadfd18).
⚠️ Report is 19 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5105      +/-   ##
==========================================
+ Coverage   68.99%   72.41%   +3.42%     
==========================================
  Files         314      315       +1     
  Lines       45857    71152   +25295     
==========================================
+ Hits        31638    51527   +19889     
- Misses      14219    19625    +5406     
Flag Coverage Δ
CI-SqlClient ?
sqlclient-pr 72.41% <ø> (?)

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

☔ View full report in Codecov by Harness.
📢 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.

@mdaigle mdaigle added the Hotfix 8.0.0 PRs that must be backported to release/8.0 label Nov 18, 2026
@mdaigle
mdaigle merged commit 880cfbc into main Nov 18, 2026
53 of 54 checks passed
@mdaigle
mdaigle deleted the dev/mdaigle/sqlclient-flaky-quarantine-1118 branch November 18, 2026 21:33
@github-project-automation github-project-automation Bot moved this from To triage to Done in SqlClient Board Nov 18, 2026
@mdaigle mdaigle added Hotfix 7.1.3 PRs targeting main that should be backported to release/7.1 for 7.1.3. Hotfix 6.1.9 PRs targeting main that should be backported to release/6.1 for 6.1.9. labels Nov 18, 2026
mdaigle added a commit that referenced this pull request Nov 19, 2026
Co-authored-by: Malcolm Daigle <mdaigle@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
mdaigle added a commit that referenced this pull request Nov 19, 2026
Co-authored-by: Malcolm Daigle <mdaigle@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
mdaigle added a commit that referenced this pull request Nov 20, 2026
Co-authored-by: Malcolm Daigle <mdaigle@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area\Tests Issues that are targeted to tests or test projects Hotfix 6.1.9 PRs targeting main that should be backported to release/6.1 for 6.1.9. Hotfix 7.1.3 PRs targeting main that should be backported to release/7.1 for 7.1.3. Hotfix 8.0.0 PRs that must be backported to release/8.0

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants