Karol Zadora-Przylecki

From the orchestrator perspective we did make a change (that will land in 8.1) that makes the shutdown of containers significantly faster. Previously it was essentially serialized, now it is...

I am not able to reproduce either. What I did: 1. Built the app that @SvenVandenbrande described here https://github.com/dotnet/aspire/discussions/4499#discussion-6817155 (web frontend, web api, Redis Postgres). 2. Run it 10 times...

@adamint sure. I just realised that there was another repro mentioned here https://github.com/dotnet/aspire/issues/4247#issuecomment-2127747960 need to try that.

OK I can definitively reproduce the problem with an UDP endpoint. Looks like DCP is crashing 😞 Investigating... Edit: I am going to open a separate issue for the repro...

> Edit: I am going to open a separate issue for the repro that [@cecilphillip](https://github.com/cecilphillip) reported, and keep open this one in case someone finds a repro for the original...

Aspire 8.1 release contains the fixes mentioned above. Closing for now; if someone encounters this again, please open a new issue.

What we can do is to have a policy preference for IPv4 or IPv6. Probably default to IPv4. I am going to open an issue about that in DCP repo.

@afscrome it is not so much "forcing IPv6", but rather a preference for IPv6 if both IPv6 and IPv4 are available. I am thinking we need a way to turn...

This is going to be fixed in 8.1 release. We are introducing a new environment variable, `DCP_IP_VERSION_PREFERENCE`, that determines which version of the IP protocol will be preferred for communicating...

@ys0d you can verify whether you have the correct DCP version by running `dcp version` from the command line (you might need to find where that exe lives in the...