Bump Polly to 8.4.1

[Martin Costello (martincostello)]

• Bump Polly to 8.4.1 to pick up bug fixes:
  • Fix retry delay going negative for large retries with exponential delays App-vNext/Polly#2164
  • Handle nested inner exceptions App-vNext/Polly#2166
• Group Polly dependabot updates to avoid multiple PRs such as:
  • Bump Polly.Core from 8.3.1 to 8.4.0 #4167
  • Bump Polly.Extensions from 8.3.1 to 8.4.0 #4200

Microsoft Reviewers: Open in CodeFlow

[Martin Costello (martincostello)]

I think the packages need mirroring.

[Dan Moseley (danmoseley)]

I thought I did.. I'll try again

[Dan Moseley (danmoseley)]

I had mirrored Polly but not Polly.Extensions.

We really need an the internal mirror process to be easier, it makes me type in every package and version number, each one is a pipeline run unless I just want latest .. maybe Jose Perez Rodriguez (@joperezr) already has a script...

[Dan Moseley (danmoseley)]

for this reason, I'm inclined to mostly ignore random updates eg AWS patch versions and then catch up for our releases. whereas this Polly update, it's clear it brings improvements we need.

[Jose Perez Rodriguez (joperezr)]

I had mirrored Polly but not Polly.Extensions.

We really need an the internal mirror process to be easier, it makes me type in every package and version number, each one is a pipeline run unless I just want latest .. maybe Jose Perez Rodriguez (@joperezr) already has a script...

Technically speaking, you can likely get away with a single run most of the time if you keep version as "latest". Given the whole point of these updates is to mirror latest on NuGet, having "latest" on the pipeline means "latest for each package available on NuGet" which is most of the time what you want with these updates. That said, I think it is great feedback, and we should ask @dotnet/dnceng to see if they can allow passing in key-value pairs instead.

[Dan Moseley (danmoseley)]

Technically speaking, you can likely get away with a single run most of the time if you keep version as "latest". Given the whole point of these updates is to mirror latest on NuGet, having "latest" on the pipeline means "latest for each package available on NuGet" which is most of the time what you want with these updates. That said, I think it is great feedback, and we should ask @dotnet/dnceng to see if they can allow passing in key-value pairs instead.

You're right that latest is 98% what we want.

OK, this seems to work -- paste in the entire list each time:
https://gist.github.com/danmoseley/0c9e188da88639fdf39e19ee02dfc722

Choosing "new or non microsoft" is fine as for Microsoft ones that simply repeats work the regular job does hourly, it adds 20 sec per package. that will get what we need 98% of the time, then we go bump the PR jobs.

It would also help if we grouped them together more coarsely, so there were fewer PR's.

[Dan Moseley (danmoseley)]

cc Ankit Jain (@radical) fyi ^^

[Dan Moseley (danmoseley)]

Looks like it takes 46 mins to do the whole lot.