Daniel Martí

Thank you - I've actually run into that panic myself just today as well, so I'll look at reducing and filing that bug.

Forgot to update this thread - that bug filed is now https://github.com/cue-lang/cue/issues/3648.

This issue affected the same project which now fails due to an error reduced in https://github.com/cue-lang/cue/issues/3850. So we will come back to this once 3850 is resolved, to see what...

Indeed. We are looking into memory usage shortly, along with https://github.com/cue-lang/cue/issues/3334. We will post updates once we have any.

Hi again @alecholmez @mxey - could you please try master again and report how memory usage looks for you now? I just posted an update at https://github.com/cue-lang/cue/issues/3334#issuecomment-3057186530.

Great to hear! Let us know if memory usage is acceptable as of master. We're not looking for perfect right now - there is still work to be done -...

@alecholmez also confirmed that the memory usage they see with master is much improved compared to evalv2, so I'll consider this issue resolved now :) More incremental improvements with memory...

Still seems to be an issue as of v0.13.0 with evalv3.

My current understanding is that required fields are a constraint applied to the exported data, so any non-exported values such as definitions or hidden fields having missing required fields should...

Labelling as "WorkingAsIntended" even though I'm not 100% sure about that suspicion. Perhaps @cuematthew can help clarify.