Ryan Fowler

I'm seeing the same problem in doom-one, doom-one-light, and doom-vibrant.

FWIW, I ran my reproduction steps on a second Macbook, and the see the same behavior.

It's worth looking at how docker-compose uses profiles. They provide a pretty nice way for users to cluster groups of services. https://docs.docker.com/compose/profiles/

In a project I maintain, I do some cleanup work in a fixture. If there's a problem, I call report with a specific file/line based on my stack because the...

I guess you could argue that. In my case, I have a function in my test code that checks status codes and calls `report` if it sees something fishy so...

Awesome! Looking forward to upgrading from 1.4.1 :)

@Nino-K This appears to still be a problem with Rancher Desktop 1.8. I don't know for sure if the same thing is making my dev environment hang, but I think...

I tried my original reproduction steps with 1.8.1 on a work M1 Macbook and a personal M1 Macbook. It's hangs on both and puts qemu into 100% CPU usage.

@Nino-K I don't think it's https://github.com/lima-vm/lima/issues/1333. That bug appears to be talking about Virtualization.Framework. Looks like Rancher Desktop uses qemu. I tried to follow my reproduction steps on lima 0.15,...

It's got to be a problem with https://github.com/lima-vm/alpine-lima. When I start a VM with `limactl start --name alpine template://alpine` the problem reproduces.