Alex Couture-Beil

It's currently possible to disable collection of analytics with `EARTHLY_DISABLE_ANALYTICS` or `DO_NOT_TRACK`, perhaps these could be extended to cover this `printf`? PRs would be welcome for this.

Another possibility would be a satellite flag that could be used when initially creating the satellite, which would deliberately remove/disable qemu from/on the satellite. We shouldn't change the current behaviour...

> Any updates or roadmap on this issue? @alexcb We've been working through some data race warnings, which are documented under https://github.com/earthly/earthly/issues/2957#issuecomment-1625808777 We'll be posting more updates under #2957 as...

#2957 has been fixed as of of [v0.7.21](https://github.com/earthly/earthly/releases/tag/v0.7.21); that issue was a race condition inside the buildkit scheduler, in particular when merging (deduplicating) multiple edges within the build graph. I...

@madsnedergaard can you confirm that your remote buildkit instance (or satellite) has also been updated to v0.7.21? If so, any sort of reproduction case for this would be incredibly helpful.

We've hear from a second user, who confirmed their satellite was indeed on v0.7.21; we'll reopen this as it doesn't seem related to the scheduler error. again, if anyone comes...

Thanks for confirming the remote version. > We will soon migrate to satellites though, so maybe that will help? It could help with greater log visibility, but unfortunately the problem...

> so is very reproducible Our ideal reproduction case would involve a clear initial cache, i.e. `earthly prune --reset`, followed by running earthly against one (or more) Earthfile targets.

This is the first time I got this error since adding 5f287a248e3bc1421048626c278eabc5e4f0f49f I ran `~/gh/earthly/earthly/ast/tests$ earthly +update-all` while dealing with a unrelated change where I was renaming `smoke.earth` to `parser-smoke.earth`...

We got a sample which includes the initial call to `loadUnlocked-add`, followed by it being `delete`ed, then followed by the final `get-edge-not-found` error: ``` sha256:7f718cfe4d99b2d0c36d11be9c3d15765002a53c9497934f3c1cbf5181495347 name=copy /code/some/path/here /some-dst-path desiredState=complete num...