-
Notifications
You must be signed in to change notification settings - Fork 61
Make "Couldn't import file" more clear. Potential bug #374
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
Comments
@artpaym Are you using sjsonnet at work too? |
@artpaym 0.5.1 has just been released, can you help test it? |
@He-Pin @stephenamar-db thanks, Let me describe what I see. I'm running sjsonnet from a WSL folder which is also managed by Nix (in case it matters): The command is:
so I'm passing a couple of tlas and passing some jsonnet source file from a subfolder. The output is (I changed folder names):
the body of
Relative to that Instead, correct location should be Does it help? @He-Pin yes we're using it at work, I'm looking for jrsonnet alternatives which we're currently calling as a standalone binary from a Java app. If sjsonnet has good speed, I'd want to try running it as a library from Java app (afaik it's possible) for even better speeds. For that I wanted to create a separate ticket as I'm confused how to do that. |
I'm trying to reproduce. Can you clarify what is in ./subfolder/src/mapper.jsonnet? How is Does the directory structure look like? ./subfolder/src/mapper.jsonnet |
There's a problem with native: Scala Native:
Scala JVM:
|
I filed a bug with os-lib |
We are using sjsonnet as a library from Spring app, which works well, hope we can share something. |
Maybe a bug in scala native library ? |
@stephenamar-db @He-Pin sounds promising, then maybe you can check this one #405 |
Does it mean a call to |
Uh oh!
There was an error while loading. Please reload this page.
Make "Couldn't import file" error more clear.
Currently it just says it failed to import a file, for example:
In the error message, add details on:
I suspect there is some bug with paths resolution, because "jsonnet" processes the same files just fine (and sjsonnet as well, but only when full absolute path is given).
I can't reproduce the bug itself, because this is a huge project, and on a smaller example sjsonnet works file, so I don't understand what's the issue exactly.
The text was updated successfully, but these errors were encountered: