Tagging subscribers to this area: @tarekgh, @safern, @krwq
Notify danmosemsft if you want to be subscribed.

Tagging subscribers to this area: @dotnet/ncl
Notify danmosemsft if you want to be subscribed.

CC @stephentoub @noahfalk

/azp run runtime-libraries outerloop

Should I be concerned about this as an indication that the activity change is a larger breaking change than anticipated?

Should I be concerned about this as an indication that the activity change is a larger breaking change than anticipated?

From what I am seeing is now storing more stuff as W3C Id format became a default. so I expect the breaking wouldn't be big in such cases (I guess). NCL may talk about this scenario better.

CC @karelz who may loop other guys can talk about that. to get @karelz up to speed, we have changed the Activity Id default Format from Heiraracal to W3C, and Http logs more info in the harder when having W3C format (e.g. transparent and tracestate fields). we have a config switch to get back the old behavior if necessary.

@noahfalk @shirhatti do you have any more input here?

/azp run runtime-libraries outerloop

Certainly there is some risk involved in making the breaking change, but this issue didn't change my assessment of it if that helps at all : )

The failures including the outerloop failures are not related. Also, this PR is addressed all Http test failures. I am going to merge this one.