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.

Sign up for GitHub

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

Retrieve whether fusion was used automatically #55

Open
FriederikeHanssen opened this issue Jul 26, 2024 · 2 comments
Open

Retrieve whether fusion was used automatically #55

FriederikeHanssen opened this issue Jul 26, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@FriederikeHanssen
Copy link
Member

Description of the bug

This function should retrieve whether fusion was used: nf-aggregate/modules/local/seqera_runs_dump/functions.nf at c9aec68034466a553a165d25cc72d1e54085cd87 · seqeralabs/nf-aggregate

However, it fails on nested config imports as done in viralrecon here: viralrecon/conf/modules.config at 3731dd3a32a67a2648ea22c2bd980c224abdaee2 · nf-core/viralrecon

The publishDir for viralrecon is resolved as

publishDir = [path:ScriptDF8044060054E44F9089B2B3ABA330E8$_run_closure2$_closure45$_closure49@4c05f83b, mode:'copy', saveAs:ScriptDF8044060054E44F9089B2B3ABA330E8$_run_closure2$_closure45$_closure50@820b78a, enabled:false]

in comparison to

publishDir = [path:{ "${params.outdir}/pipeline_info" }, mode:'copy', pattern:'*_versions.yml']

which causes the ConfigSlurper to fail.

It seems there is currently no direct way to retrieve this information via the API and the recommended way is from the resolved configs.

Command used and terminal output

No response

Relevant files

No response

System information

No response
@FriederikeHanssen FriederikeHanssen added the bug Something isn't working label Jul 26, 2024
@FriederikeHanssen FriederikeHanssen mentioned this issue Jul 26, 2024
Closed
@pditommaso
Copy link

This approach is not scalable (from a maitenance point of view) and just creates tech debt. Please talk with Nextflow team to solve this problem

@drpatelh
Copy link
Member

drpatelh commented Jul 26, 2024 •
edited
Loading

Better solution here https://github.com/seqeralabs/platform/issues/7423 to add Fusion and Wave execution metadata to describe workflow endpoint. Waiting on implementation.

@drpatelh drpatelh mentioned this issue Jul 26, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pditommaso @FriederikeHanssen @drpatelh