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

[Bug] The configuration unification at compile time does not meet the expectation when the attribute with the same name has a syntax node of non-configured type e.g. ConfigExpr and SchemaExpr #422

Closed
Peefy opened this issue Feb 22, 2023 · 0 comments · Fixed by #423
Assignees
Labels
bug Something isn't working resolver

Comments

@Peefy
Copy link
Contributor

Peefy commented Feb 22, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Write the kcl code (main.k)

schema Resource:
    cpu: int
    memory: str

schema Config:
    resource: Resource

r = Resource {
    cpu = 4
    memory = "8Gi"
}

config: Config {
    resource: Resource {
        cpu = 2
        memory = "4Gi"
    }
}

config: Config {
    resource: r
}

Then run the command:

kclvm_cli run main.k

2. What did you expect to see? (Required)

r:
  cpu: 4
  memory: 8Gi
config:
  resource:
    cpu: 4
    memory: 8Gi

3. What did you see instead (Required)

r:
  cpu: 2
  memory: 4Gi
config:
  resource:
    cpu: 2
    memory: 4Gi

4. What is your KusionStack components version? (Required)

kclvm version is 0.4.5; checksum: c5339e572207211e46477825e8aca903

@Peefy Peefy added bug Something isn't working resolver labels Feb 22, 2023
@Peefy Peefy added this to the v0.4.5 Release milestone Feb 22, 2023
@Peefy Peefy self-assigned this Feb 22, 2023
@Peefy Peefy changed the title [Bug] The configuration unification at compile time does not meet the expectation when there is a temporary expression in the configuration. [Bug] The configuration unification at compile time does not meet the expectation when the attribute with the same name has a syntax node of non-configured type e.g. ConfigExpr and SchemaExpr Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resolver
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant