Skip to content
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

CUE_EXPERIMENT=evalv3 on v0.11.0-alpha.4 breaks previously working cue project #3546

Open
cds-amal opened this issue Nov 2, 2024 · 1 comment
Assignees
Labels
NeedsInvestigation Triage Requires triage/attention

Comments

@cds-amal
Copy link

cds-amal commented Nov 2, 2024

What version of CUE are you using (cue version)?

$ cue version
cue version v0.11.0-alpha.4
                                                                                                                                                                                                                                                                                                          
go version go1.22.4
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH arm64
            GOOS darwin
cue.lang.version v0.11.0

Does this issue reproduce with the latest stable release?

No

What did you do?

  1. Check out this repo: https://github.com/cds-io/din-cue
  2. run make build for baseline (no error)
  3. run CUE_EXPERIMENT=evalv3 make build for error

What did you expect to see?

I expected yml and sol files to be created.

What did you see instead?

Unify / constraint errors

CUE_EXPERIMENT=evalv3 make build
        ...chains
        ...providers
_loganProvider.services.blast.mainnet.endpoint_details.headers: field not allowed:
    ../config/provider.cue:36:5
_loganProvider.services.blast.mainnet.endpoint_details.priority: field not allowed:
    ../config/provider.cue:35:5
_nodiesProvider.services.blast.mainnet.endpoint_details.priority: field not allowed:
    ../config/provider.cue:52:6
_zheProvider.services.mantle.mainnet.endpoint_details.headers: field not allowed:
    ../config/provider.cue:69:5
providers.Logan.services.blast.mainnet.endpoint_details.headers: field not allowed:
    ../config/provider.cue:36:5
providers.Logan.services.blast.mainnet.endpoint_details.priority: field not allowed:
    ../config/provider.cue:35:5
providers.Nectarine.services.blast.mainnet.endpoint_details.priority: field not allowed:
    ../config/provider.cue:52:6
providers.Zhe.services.mantle.mainnet.endpoint_details.headers: field not allowed:
    ../config/provider.cue:69:5
_berryProvider.services.optimism.mainnet.caps: field not allowed:
    ./utils.cue:47:17
    ./utils.cue:49:7
_berryProvider.services.optimism.mainnet.methods: field not allowed:
    ./utils.cue:47:17
    ./utils.cue:50:7
_berryProvider.services.optimism.mainnet.network_uri: field not allowed:
    ./utils.cue:47:17
    ./utils.cue:48:7

<SNIP> ... the same error is repeated for other files (network_uri, methods, and caps) field not allowd

make[1]: *** [build] Error 1
make: *** [build] Error 2
                                                                                                                                                                                                                                                                                                          
grue in din-cue on  main [✘!] via .NET took 44s
@cds-amal cds-amal added NeedsInvestigation Triage Requires triage/attention labels Nov 2, 2024
@mvdan mvdan self-assigned this Nov 4, 2024
@cds-amal
Copy link
Author

cds-amal commented Nov 9, 2024

Verified this issue still exists in v0.11.0-alpha.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Triage Requires triage/attention
Projects
None yet
Development

No branches or pull requests

2 participants