Skip to content

Clarify ObjectInstance behavior when no owning object is available - #131900

Merged
ViveliDuCh merged 4 commits into
dotnet:mainfrom
ViveliDuCh:dev/vivianad/objectinstance-remarks-update
Aug 7, 2026
Merged

Clarify ObjectInstance behavior when no owning object is available#131900
ViveliDuCh merged 4 commits into
dotnet:mainfrom
ViveliDuCh:dev/vivianad/objectinstance-remarks-update

Wording consistency with api-docs

9c1d380
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Aug 7, 2026 in 9h 3m 15s

Build #20260806.121 had test failures

Details

Tests

  • Failed: 1 (0.00%)
  • Passed: 1,296,075 (98.04%)
  • Other: 25,899 (1.96%)
  • Total: 1,321,975

Annotations

Check failure on line 623 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L623

Helix Job Monitor timed out after 535 minute(s) (08:55:00). 7 Helix job(s) were unfinished or unprocessed:

Check failure on line 1666 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L1666

Bash exited with code '1'.

Check failure on line 1 in System.Net.Sockets.Tests.SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Net.Sockets.Tests.SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds

Assert.False() Failure\nExpected: False\nActual:   True
Raw output
at System.Net.Sockets.Tests.SocketBlockingModeTransitionTests.ConnectAsync_WithBuffer_Succeeds() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/Connect.Unix.cs:line 230
--- End of stack trace from previous location ---