-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add rworkflows #105
Add rworkflows #105
Conversation
.github/workflows/R-CMD-check.yaml
Outdated
- name: Install Python dependencies for reticulate | ||
run: | | ||
reticulate::install_miniconda() | ||
reticulate::py_install(c("anndata", "scanpy"), pip = TRUE) | ||
shell: Rscript {0} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will neurogenomics/rworkflows@master
also install these packages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to log our in-person discussion here, we talked about strategies for installing miniconda
/anndata
/scanpy
.
Here are some of the proposed options:
- Trigger the
setup_conda
function whenever aAnnDataR
function that requiresminiconda
/anndata
/scanpy
is used. We use this strategy for non-R dependencies inMAGMA.Celltyping
, which requires the command line toolMAGMA
for certain functions. The goal in that case is to remove any manual setup steps for the user. However, in the case of GHA, the only place that this would currently be triggered withinAnnDataR
is the unit tests, which @rcannood was opposed to. From a philosophical standpoint I have less of an issue with additional installs being triggered post-AnnDataR
installation, but I do have some practical concerns that R might have some trouble using thereticulate
conda env right after it's been created. For this reasonbasilisk
might be a better option, which switches between envs much more smoothly. - Add an optional step to rworkflows action to setup a conda env (I've actually been meaning to add this feature since its inception). Might be the best option tho, and shouldn't be too hard to implement (famous last words)
- On GHA, skip any tests that require
miniconda
/anndata
/scanpy
. Not a very good option, since it creates a huge blindspot during testing. - Revert to the original GHA workflows and remove
rworkflows
. Easy short-term solution, but less so for the long-term.
Can you merge the main branch into this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR contains a lot of changes which are not relevant to the rworkflows CI. I feel like this PR should only make changes to the .github folder (and maybe the README or the DESCRIPTION).
I was a bit too optimistic about my other PR and thought that would become "main" quite soon. Seems like those changes are going to take a while to break up and review, so i can change this PR back. |
Closing this PR for now |
anndataR 0.99.0
New features
rworkflows
CI.actions/checkout@v4
(which has less issues).setup_conda
automatically installs minicondaand sets up conda env: Automatically setup conda env #97