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

Updated shinyngs containers and nftest snaps #7323

Merged
merged 5 commits into from
Jan 17, 2025
Merged

Conversation

nschcolnicov
Copy link
Contributor

PR checklist

Closes #XXX

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the module conventions in the contribution docs
  • If necessary, include test data in your PR.
  • Remove all TODO statements.
  • Emit the versions.yml file.
  • Follow the naming conventions.
  • Follow the parameters requirements.
  • Follow the input/output options guidelines.
  • Add a resource label
  • Use BioConda and BioContainers if possible to fulfil software requirements.
  • Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
    • For modules:
      • nf-core modules test <MODULE> --profile docker
      • nf-core modules test <MODULE> --profile singularity
      • nf-core modules test <MODULE> --profile conda
    • For subworkflows:
      • nf-core subworkflows test <SUBWORKFLOW> --profile docker
      • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
      • nf-core subworkflows test <SUBWORKFLOW> --profile conda

@nschcolnicov
Copy link
Contributor Author

nf-test for validatefomcomponents depends on the approval of this PR: nf-core/test-datasets#1465

@@ -15,8 +15,8 @@ process SHINYNGS_APP {

conda "${moduleDir}/environment.yml"
container "${ workflow.containerEngine == 'singularity' && !task.ext.singularity_pull_docker_container ?
'https://depot.galaxyproject.org/singularity/r-shinyngs:2.0.0--r43hdfd78af_0' :
'biocontainers/r-shinyngs:2.0.0--r43hdfd78af_0' }"
'https://community-cr-prod.seqera.io/docker/registry/v2/blobs/sha256/97/971684ed03cda2689eea7db9e7f2ee74d079ddd74e3a3baac31e958eea6feb0e/data' :
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice- was going to suggest this

@@ -2,4 +2,5 @@ channels:
- conda-forge
- bioconda
dependencies:
- bioconda::r-shinyngs=2.0.0
- bioconda::r-shinyngs=2.1.0
- conda-forge::r-base=4.4.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume this pin is there to fix the snapshots.

Actually, I think we should just take the R version out of the version outputs from the modules. I hadn't appreciated when I wrote the modules that it would be disruptive, and I don't think there's a good reason to pin R otherwise.

We will in due course have lockfiles in nf-core to cover the real use case for this sort of thing.

@nschcolnicov nschcolnicov added this pull request to the merge queue Jan 17, 2025
@nschcolnicov nschcolnicov removed this pull request from the merge queue due to a manual request Jan 17, 2025
@nschcolnicov nschcolnicov added this pull request to the merge queue Jan 17, 2025
Merged via the queue into master with commit 90ac6ed Jan 17, 2025
96 checks passed
@nschcolnicov nschcolnicov deleted the bump_shinyngs_2.1.0 branch January 17, 2025 14:24
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 this pull request may close these issues.

3 participants