-
Notifications
You must be signed in to change notification settings - Fork 290
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
internal/core/export: UpCount nil dereference panic #3489
Comments
@yujunz are you able to provide us with CUE code to reproduce this panic? |
The CUE code it pretty complex with deep import chain. I can try to narrow down since Or shall I try evalv3 since it seems an evaluation error? |
If you could try evalv3 that would also be helpful, yes. Although we would still like to fix any panics in evalv2. |
It may take some time to narrow down the error, but do you have any quick hint which could be the root cause of panic in current version? |
Could this be the culprit?
from
while it is tested OK in https://cuelang.org/play/?id=VXxtPsG0DAO#w=function&i=cue&f=eval&o=cue The full configurations includes much more in |
Is the code public? If so, could you share a link? If not, would you be able to share it with us privately so that we can reproduce the crash, as well as all the evalv3 issues to be fixed? |
Unfortunately not. It's a huge private mono repo. I'll try to narrow down to a sharable subset to reproduce and share. |
I'm able to narrow down it a bit to one type of error See also https://gist.github.com/yujunz/310b4e462432b63faf9c4ce1dca06534 for the related part of
|
Please let us know when you do find a smaller reproducer you can share with us. Because ideally we want bug fixes to be paired with a regression test. Plus, a reproducer is also useful to debug what's going wrong. |
Trying to fix it blindly
Reduces error to one.
But after removing metadata
evalv3 crashed 🫠
|
What version of CUE are you using (
cue version
)?Does this issue reproduce with the latest stable release?
Yes
What did you do?
cue eval
What did you expect to see?
eval output
What did you see instead?
The text was updated successfully, but these errors were encountered: