We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello @Peefy! I believe I hit an odd bug.
version: 0.8.8-linux-amd64
kcl.mod is at repo root. When we invoke kcl and don't hop over kcl.mod everything is fine:
time kcl -dY kcl.yaml ../../bootstrap.k hello: world: 1234 kcl -dY kcl.yaml ../../bootstrap.k 0.05s user 0.03s system 35% cpu 0.234 total
If there's kcl.mod on the way, networking kicks, dns queries etc probably related to some module operations... Clearly seen from strace.
time kcl -dY kcl.yaml ../../../bootstrap.k hello: world: 1234 kcl -dY kcl.yaml ../../../bootstrap.k 0.08s user 0.04s system 1% cpu 11.133 total
The path can actually be absolute, so it looks like it happens when we run into a module with remotes on the way to the code k file.
Thank you!
The text was updated successfully, but these errors were encountered:
Dup with kcl-lang/kpm#328
Sorry, something went wrong.
it was moved) okay thank you. I thought i haven't posted)
No branches or pull requests
Hello @Peefy! I believe I hit an odd bug.
version: 0.8.8-linux-amd64
kcl.mod is at repo root. When we invoke kcl and don't hop over kcl.mod everything is fine:
If there's kcl.mod on the way, networking kicks, dns queries etc probably related to some module operations... Clearly seen from strace.
The path can actually be absolute, so it looks like it happens when we run into a module with remotes on the way to the code k file.
Thank you!
The text was updated successfully, but these errors were encountered: