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

Jump to bottom

View versions subcommand fails for packages that use legacy NuGet versioning #7

Closed
cgranade opened this issue Aug 24, 2021 · 2 comments
Closed

View versions subcommand fails for packages that use legacy NuGet versioning #7

cgranade opened this issue Aug 24, 2021 · 2 comments

Comments

@cgranade
Copy link

When running ruget view versions for a package that uses legacy NuGet versioning (e.g.: 0.4.1901.2905), ruget fails with a ruget::api::bad_json diagnostic:

$  cargo +nightly run -- view versions Microsoft.Quantum.IQSharp
    Finished dev [unoptimized + debuginfo] target(s) in 0.44s
     Running `target\debug\ruget.exe view versions Microsoft.Quantum.IQSharp`
Error: ────[ruget::api::bad_json]────────────────────

    × Received some bad JSON from the source. Unable to parse.
    ╰─▶ missing field `foo` at line 1 column 1648

   ╭───[https://api.nuget.org/v3/registration5-gz-semver2/microsoft.quantum.iqsharp/index.json:1:1607] JSON context...:
 1 │ rp"],"title":"","version":"0.4.1901.2905"},"packageContent":"https://api.nuget.o
   ·                                         ┬
   ·                                         ╰─ here

    ‽ This is a bug. It might be in ruget, or it might be in the source you're using, but it's definitely a bug and should be reported.

error: process didn't exit successfully: `target\debug\ruget.exe view versions Microsoft.Quantum.IQSharp` (exit code: 1)
@zkat
Copy link
Owner

zkat commented Aug 24, 2021

Sorry, this was a debugging thing that got left in while I was working on miette stuff. Should be fine if you pull now :)

@zkat zkat closed this as completed Aug 24, 2021
@cgranade
Copy link
Author

Oh, awesome, thank you! ♥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zkat @cgranade