-
Notifications
You must be signed in to change notification settings - Fork 301
Issues: cue-lang/cue
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
evalv3: another "undefined field" regression
evaluator
evalv3
issues affecting only the evaluator version 3
#3699
opened Jan 24, 2025 by
mvdan
evalv3: (x & y).z pattern error at current master
evaluator
evalv3
issues affecting only the evaluator version 3
NeedsInvestigation
#3685
opened Jan 18, 2025 by
loisch
eval: unification rule doesn't hold (X & X != X)
evaluator
evalv3
issues affecting only the evaluator version 3
NeedsInvestigation
#3675
opened Jan 13, 2025 by
loisch
evalv3: Different result v0.12 vs 0.11
evaluator
evalv3
issues affecting only the evaluator version 3
NeedsInvestigation
#3672
opened Jan 11, 2025 by
loisch
evalv3: cycle error becomes an empty error in the new evaluator
evaluator
evalv3
issues affecting only the evaluator version 3
#3669
opened Jan 9, 2025 by
mvdan
eval: matchN unification succeeds even with impossible schema combinations
evaluator
NeedsInvestigation
#3663
opened Jan 9, 2025 by
rogpeppe
evalv3: enable evalv3 by default
evaluator
evalv3
issues affecting only the evaluator version 3
FeatureRequest
New feature or request
#3662
opened Jan 9, 2025 by
myitcv
eval: matchN reference to closed list does not close contents of list
evaluator
NeedsFix
#3659
opened Jan 8, 2025 by
rogpeppe
Performance: Evaluation of 200 lines takes >130s
evaluator
NeedsInfo
More information or clarification needed from the user
#3654
opened Jan 5, 2025 by
loisch
"not properly initialized" error regression in evalv3 involving builtins
evaluator
evalv3
issues affecting only the evaluator version 3
#3648
opened Jan 3, 2025 by
mvdan
"field not allowed" potential regression in evalv3, also with a confusing error path
evaluator
evalv3-win
Issues resolved by switching from evalv2 to evalv3
NeedsDecision
#3637
opened Dec 30, 2024 by
mvdan
evalv3: structural cycle regression involving a builtin and repeated schemas
evaluator
evalv3
issues affecting only the evaluator version 3
#3634
opened Dec 24, 2024 by
mvdan
evalv3: repeated use of schema causes wall time and memory use to blow up
evaluator
evalv3
issues affecting only the evaluator version 3
#3633
opened Dec 24, 2024 by
mvdan
sortfields does not sort some struct fields in
cue eval
when there are cyclic references
evaluator
#3622
opened Dec 11, 2024 by
mvdan
evalv2: panic in cuelang.org/go/internal/core/adt.(*Vertex).DerefValue
evaluator
NeedsInvestigation
panic
#3570
opened Nov 10, 2024 by
bobcallaway
eval: poor performance with large disjunction and matchIf
evaluator
evalv3-win
Issues resolved by switching from evalv2 to evalv3
#3514
opened Oct 15, 2024 by
rogpeppe
internal/core/export: UpCount nil dereference panic
evaluator
NeedsInfo
More information or clarification needed from the user
NeedsInvestigation
panic
#3489
opened Oct 10, 2024 by
yujunz
embedding a definition list at the top level seems to disregard closedness rules
closedness
evaluator
NeedsFix
#3487
opened Oct 9, 2024 by
mvdan
eval: recursive matchN call runs out of memory
evaluator
evalv3-win
Issues resolved by switching from evalv2 to evalv3
#3477
opened Oct 3, 2024 by
rogpeppe
eval: stack overflow with cue def
evaluator
evalv3-win
Issues resolved by switching from evalv2 to evalv3
NeedsFix
#3476
opened Oct 3, 2024 by
rogpeppe
evaluator: parsing antler CUE configs can exhaust system memory
evaluator
NeedsInvestigation
#3452
opened Sep 13, 2024 by
heistp
eval:
matchN
with noncrete value should yield error but does not
evaluator
NeedsInvestigation
#3439
opened Sep 5, 2024 by
myitcv
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.