-
Notifications
You must be signed in to change notification settings - Fork 170
0.14 generates invalid cue (block quotes) #173
Comments
Perhaps related to the re-formatting: cue 0.14 is massively slower than 0.11 for running vet and eval. Something that completed quickly previously now takes over a minute! |
Actually, even my dump-yaml command is slow. My dry-run went from a few seconds to a few minutes. |
I down-graded to 0.12 and things are fast again. |
Do you have a file with which I could reproduce the slowness so I can profile it? |
I can create one. Have you compared the execution speed of the new release to the old one? |
I don't see noteworthy differences myself between the two. So it would be useful to have something that would cause this problem. |
I'm a bit surprised the comments are generated back. Pre-1.14 |
I can't reproduce the slowness now, but the difference may be that I am not creating a cue.mod directory anymore, but just have a cue.mod file (which seems to be working on 0.14) Can you reproduce the block quote issue? I am installing cue and the libs as per https://gist.github.com/gregwebs/0fe911ac02d06bf65c66b88c4293b85e |
I'm at KubeCon now with intermittent availability, but will try asap. Regarding the slowness. I would really like to find the slowness issue before the next release. Does any of your parent directories have a lot of files in them (of any type), by any chance? If that's the case it may be a regression. |
It is a lot easier for me to try to reproduce the slowness issue if I can get over the block quotes issue first and actually upgrade to 0.14 (but not switch to the new cue.mod directory format until this issue is properly tested). |
Now KubeCon is over I'll try to give this some attention hopefully today. (I did try quickly before but didn't succeed). |
I could not reproduce it with the script. I noticed that K8s recently removed some block comments in package docs, so figured that maybe we are importing different versions of k8s (e.g. if this is run in the context of a go.mod). I've indeed found that package docs were in a different code path in |
Pass package comments through writeDoc. Issue #173 Change-Id: Ib0438ed38012bcb15128d1315b654111285753d9 Reviewed-on: https://cue-review.googlesource.com/c/cue/+/4140 Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>
So to fix this you can fetch the latest K8s files or sync to tip for CUE. |
The bug reported by this has been fixed. |
This issue has been migrated to cue-lang/cue#173. For more details about CUE's migration to a new home, please see cue-lang/cue#1078. |
In my cue file
Cue vet says
I tried
rm -r cue.mod/gen
. I also tried tocue go get
the packages.If I
cue fmt
the code that seems to temporarily fix the problem, but eventually the formatting gets reverted.The text was updated successfully, but these errors were encountered: