You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the new evaluator first does something very weird - cue eval exits successfully without printing anything at all, not even the hello: "world". This seems like a hard bug; if something went wrong, something is swallowing the error.
> env CUE_EXPERIMENT=evalv3=1
> exec cue eval
Then the cue export does show us the cyclic reference errors.
> exec cue export
[stderr]
inner.inner2.create_default: cyclic reference to field inner2:
./input.cue:5:1
inner.inner2.description: cyclic reference to field inner2:
./input.cue:5:1
inner.inner2.name: cyclic reference to field inner2:
./input.cue:5:1
inner.inner2.privacy: cyclic reference to field inner2:
./input.cue:5:1
But why? evalv2 handled this input just fine. Moreover, just removing the if true comprehension to inline its contents as follows seems to resolve the cyclic reference errors, which seems like a bug:
hello: "world"
outer: [Name=string]: name: Name
inner: inner2: {
name: "Employees"
description: "All employees"
privacy: "secret"
create_default: false
}
outer: outer2: {
bar: (inner.inner2.name)
}
The text was updated successfully, but these errors were encountered:
As of 0e99c20, the old evaluator evals and exports fine:
However, the new evaluator first does something very weird -
cue eval
exits successfully without printing anything at all, not even thehello: "world"
. This seems like a hard bug; if something went wrong, something is swallowing the error.Then the
cue export
does show us the cyclic reference errors.But why? evalv2 handled this input just fine. Moreover, just removing the
if true
comprehension to inline its contents as follows seems to resolve the cyclic reference errors, which seems like a bug:The text was updated successfully, but these errors were encountered: