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

Unable to deserialize lockfile #27

Closed
pswaminathan opened this issue May 25, 2024 · 2 comments · Fixed by #29
Closed

Unable to deserialize lockfile #27

pswaminathan opened this issue May 25, 2024 · 2 comments · Fixed by #29

Comments

@pswaminathan
Copy link

pswaminathan commented May 25, 2024

$ RUST_BACKTRACE=1 multitool --lockfile multitool.lock.json update
thread 'main' panicked at src/main.rs:206:41:
Unable to deserialize lockfile: Error("invalid type: string \"https://raw.githubusercontent.com/theoremlp/rules_multitool/main/lockfile.schema.json\", expected struct Binary", line: 2, column: 100)
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: multitool::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
{
  "$schema": "https://raw.githubusercontent.com/theoremlp/rules_multitool/main/lockfile.schema.json",
...

I can provide the rest of the lockfile if needed, but I am not sure think it matters—even when I strip away everything else, it still fails. Looks like the parsing expects there to be only Binary declarations, not the "$schema".

@pswaminathan pswaminathan changed the title CLI Can't parse Lockfile Unable to deserialize lockfile May 25, 2024
@mark-thm
Copy link
Contributor

Released in 0.3.0.

@pswaminathan
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants