#Not sure what the status of
twilit sentinel
Can't actually see the error for some reason (see screenshot) but will repro
ah it's cause the trace is too big, that sort of thing will be fixed once https://github.com/dagger/dagger.io/pull/4892 is merged (all test spans will be pre-fetched)
it's in TestUserDefaults/TestSimple/inner_envfile
warped apex
Likely related to known issues with module typedefs writing an id to a file in a container, but the fact that it is creating a situation where you're stuck is new and more bad
warped apex
Dunno why but when I try to run off your branch I get these errors...
✘ withExec git fetch --tags 2.2s ERROR
┃ From https://github.com/vito/dagger
┃ * branch interfaces -> FETCH_HEAD
┃ * [new tag] helm/chart/v0.12.2 -> helm/chart/v0.12.2
┃ * [new tag] sdk/cue/v0.2.232 -> sdk/cue/v0.2.232
┃ ! [rejected] sdk/go/v0.3.1 -> sdk/go/v0.3.1 (would clobber existing tag)
┃ * [new tag] v0.16.0-llm.1 -> v0.16.0-llm.1
┃ * [new tag] v0.17.0-llm.1 -> v0.17.0-llm.1
┃ * [new tag] v0.17.0-llm.2 -> v0.17.0-llm.2
┃ * [new tag] v0.17.0-llm.3 -> v0.17.0-llm.3
┃ * [new tag] v0.17.0-llm.7 -> v0.17.0-llm.7
┃ * [new tag] v0.17.0-llm.9 -> v0.17.0-llm.9
┃ ! [rejected] v0.2.22 -> v0.2.22 (would clobber existing tag)
┃ ! [rejected] v0.9.0 -> v0.9.0 (would clobber existing tag)
┃ * [new tag] v0.99.10 -> v0.99.10
! exit code: 1
will see if I can repro it some other way
warped apex
Dunno why but when I try to run off your branch I get these errors...
```
✘ wi...
Got passed this now but can't repro the error, which commit should I be used @twilit sentinel ? cf83871cce3725eb6e7a8cc064ffa35814e76c03 doesn't exist on that branch for me
twilit sentinel
probably went away from a rebase - try git fetch vito cf83871cce3725eb6e7a8cc064ffa35814e76c03?
(hopefully github's git graph still knows about it)
twilit sentinel
Got passed this now but can't repro the error, which commit should I be used <@1...
i just pushed it to interfaces-repro if the fetch trick didn't work
warped apex
I got it now and repro'd!