Erik Sipsma

Ah well, speak of the devil: https://dagger.cloud/dagger/traces/49a0fd005179147817c927d79ba7179c Didn't look in detail yet but wondering if other tests just need the same fix as #8574 (cc @grouville)

I managed to repro this in CI with a sleep added so I could nsenter into the container and found what seems like it must be a bug in go's...

Okay managed to repro in CI again, tar up the whole rootfs, upload to s3 to exfiltrate it out, and then turn into a docker image that reproduces the problem...

Issue in go repo: https://github.com/golang/go/issues/69179

This one is not causing a flake anymore after https://github.com/dagger/dagger/pull/8470 was merged. However, it's worth leaving open since it's fixed by disabling the go mod index in our test suite,...

We got a report of users hitting this now. We haven't noticed any downsides to disabling goindex in our CI so it's worth considering making this the default setting now....

Apparently github is having issues atm w/ actions (https://www.githubstatus.com/), so probably not a good time to work on this. Will pick back up again later (cc @jedevc, seems like we...

MacOS doesn't run in PRs but ran successfully in a temp workflow here, so think this should work on main now 🤞: https://github.com/dagger/dagger/actions/runs/11352050252/job/31573962144?pr=8687

This seems to have degraded further to the point where I can't find the last time it succeeded on main. It always either fails on the ssh install step or...

100% agree with scrubbing this from the OTEL logs and agree with scrubbing it from CLI output *other than* the one case where a user explicitly asks for the CLI...