Daniel Martí

Did you by any chance test older CUE versions? It would be interesting to see if this was a regression between v0.5.0 and v0.6.0, for example. Certainly a bug to...

I also wonder why the earlier fix at https://review.gerrithub.io/c/cue-lang/cue/+/542725 wouldn't be enough here; we should be sorting the files as we load them, so the order they are fed in...

> I also wonder why the earlier fix at https://review.gerrithub.io/c/cue-lang/cue/+/542725 wouldn't be enough here; we should be sorting the files as we load them, so the order they are fed...

This still seems to happen as of 2c01ee545f1106217120764b57b1441959cc5481, with evalv3. Here is a simplified reproducer: ``` exec cue export . exec mv c.cue a.cue exec cue export . -- b.cue...

Still seems to happen as of v0.13.0 on evalv3: ``` # evalv2 env CUE_EXPERIMENT=evalv3=0 ! exec cue export in.cue # evalv3 env CUE_EXPERIMENT=evalv3=1 ! exec cue export in.cue -- in.cue...

FWIW I did not find this issue when filing https://github.com/cue-lang/cue/issues/3991 because of the lack of keywords, so: one of the issues here relates to empty comments being rendered as if...

Per my last review of https://review.gerrithub.io/c/cue-lang/cue/+/1199496 I actually think the help text was right in the original version; combining `--list` and `--path` is a supported behavior. From my reading of...

Note that this is likely a duplicate of https://github.com/cue-lang/cue/issues/1790. The title talks about comments, but that panic happens with any YAML input containing no value at all.

Also noting that https://github.com/cue-lang/cue/issues/2721 is extremely similar too.

As @antong explains, the umask behavior is correct. It declares the maximum permissions that newly created files should have, not the exact ones. I'll send a patch shortly about documenting...