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

rig library (add|default) panic #231

Open
lianos opened this issue Apr 30, 2024 · 1 comment
Open

rig library (add|default) panic #231

lianos opened this issue Apr 30, 2024 · 1 comment
Labels
bug an unexpected problem or unintended behavior

Comments

@lianos
Copy link

lianos commented Apr 30, 2024

I'm a n00b with rig but I dig the idea.

I'm trying to wrap my head around it, and want to tie a specific library as a default for a particular R version. Lots of my work leverages bioconductor mojo, so I'm also interested in tying default libraries to default versions based on their norms as well.

So, the current release of bioconductor is 3.18, and is tied to R version 4.3 ... they will upgrade to 3.19 (with R4.4 any day now, tho).

So I'm currently using R 4.3:

$ rig list
* name       version    aliases
------------------------------------------
  4.2-arm64  (R 4.2.2)
* 4.3-arm64  (R 4.3.3)
  4.4-arm64  (R 4.4.0)  release

And I'd like to set a bioc3.18 library as the default for R 4.3:

$  rig library list                                                                                                                                                                                                                                                                                             
bioc3.18
main (default)

So I do:

$ rig library default bioc3.18

But I'm greeted with this error:

thread 'main' panicked at /Users/gaborcsardi/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_builder-4.5.2/src/parser/error.rs:32:9:
Mismatch between definition and access of `lib-name`. Could not downcast to TypeId { t: 324675245860759320943513204350442872190 }, need to downcast to TypeId { t: 9468522667427391105921880143968470858 }

Now I reckon I may have cast the wrong rig library default spell, but I feel like that particular error message is telling me there's something else cooking that could use a fix either way :-)

Thanks!

@gaborcsardi
Copy link
Member

This is a bug indeed, thanks for reporting it! Using the previous version of rig will probably fix this, if you can install that.

@gaborcsardi gaborcsardi added the bug an unexpected problem or unintended behavior label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants