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

dylib symbol not found in the same package schema statement #86

Closed
Peefy opened this issue Jun 9, 2022 · 0 comments · Fixed by #87
Closed

dylib symbol not found in the same package schema statement #86

Peefy opened this issue Jun 9, 2022 · 0 comments · Fixed by #87
Assignees
Labels
bug Something isn't working resolver

Comments

@Peefy
Copy link
Contributor

Peefy commented Jun 9, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

KCL code structure

├── hello.k
└── pkg
    └── pkg.k
  • hello.k
import pkg

person = pkg.Person {}
  • pkg/pkg.k
schema Name:
    name?: str
    
schema Person:
    name?: Name = Name {name = "Alice"}

run:

kcl hello.k --target native

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

The YAML output

person:
   name: Alice

3. What did you see instead (Required)

The panic info:

Symbol not found: _$pkg.$Name.11\n Referenced from: /.kclvm/cache/0.4.2-e07ed7af0d9bd1e86a3131714e4bd20c/pkg.dylib

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

kclvm version is 0.4.2; checksum: e07ed7af0d9bd1e86a3131714e4bd20c

@Peefy Peefy added bug Something isn't working resolver labels Jun 9, 2022
@Peefy Peefy added this to the v0.4.3 Release milestone Jun 9, 2022
@Peefy Peefy self-assigned this Jun 9, 2022
@Peefy Peefy changed the title dylib symbol not found in the same package scheam statement dylib symbol not found in the same package schema statement Jun 15, 2022
@Peefy Peefy closed this as completed in #87 Jun 28, 2022
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