File Export Issue

[barren cloak]

@south river is this a bug? I am not familiar enough with how wingy is using

https://github.com/pjmagee/dagger-dotnet-sdk/blob/main/main.go#L22

to me looks like a simple dagger call of a function and me trying to export a *dagger.File somehow, when it exports its trying to chown?

[south river]

File Export Issue

[barren cloak]

i generated it by using WSL so its not blocking, wingy deleted that file because it should be maanged by dagger to do the introspection.

so i was like "hey, i need that file!" and then i ran the command

[south river]

@barren cloak are you hooked up to Traces by chance, would be great to be able to look at that when the function is called.

[barren cloak]

oh, dagger cloud?

[south river]

Yeah -

If not its ok, could you just share the command you ran so I can try to reproduce?

Also you running windows CLI or WSL cli?

[barren cloak]

or do you mean OTEL is not disabled?

I was running dagger windows CLI, and workaround is WSL cli

[south river]

Thanks, its possibly a bug, ill dig in a bit here.

[barren cloak]

dagger call introspect export --path ./Dagger.SDK/introspection.json

im on traces now

[south river]

Oh sweet, could you send a URL - normally folks cant see it but everyone at dagger can 😇

[barren cloak]

are you going to hack me

[south river]

Hahahaha

[barren cloak]

sorry, always a funny querstion non tech people have asked me :S

i cant help myself

[barren cloak]

sure I'll dm you

or is it actually okay to paste it here even?

[south river]

Thanks @barren cloak this is indeed a bug, im filing a report will link it here.

Interestingly enough this only seems to be a problem for files, I was able to export a dir without any issues.

[south river]

filed these two

• the issue you raised https://github.com/dagger/dagger/issues/7558

• how bad the output is on Windows whenever there is an error 😦
  https://github.com/dagger/dagger/issues/7559