[release/8.0-staging] Fix logging formatting

[tarekgh]

Backport of #106283 to release/8.0-dtaging

/cc @tarekgh

Customer Impact

Users of the .NET logging system may encounter incorrect log entries when attempting to log more than one collection argument. Instead of logging the individual values of the collection, the type name of the collection is logged. Examples of this issue can be found at #103338.

This is a regression in .NET 8.0

Details

We had some performance improvements in the logging formatting code that caused this regression.

Testing

Passed the regression tests and added more tests to cover the failing cases.

Risk

Low. This change only addresses the broken cases in the logging formatting code. It doesn't alter any logic; it simply ensures that collection formatting is corrected.

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.
• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-extensions-logging
See info in area-owners.md if you want to be subscribed.

[tarekgh]

CC @ericstj @artl93

[ergunr]

Envoyé de mon iPhone Le 25 août 2024 à 22:29, Tarek Mahmoud Sayed ***@***.***> a écrit :  Merged #106367<#106367> into release/8.0-staging. — Reply to this email directly, view it on GitHub<#106367 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUW2LQ7JAW24KB4JMVGR27TZTIV77AVCNFSM6AAAAABMO57HQOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGAYDKMJRGA4TIMQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[tarekgh]

@ergunr are you trying to communicate something on this change?