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

multiqc_data group #100

Open
thomasmanke opened this issue Oct 31, 2024 · 2 comments
Open

multiqc_data group #100

thomasmanke opened this issue Oct 31, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@thomasmanke
Copy link
Contributor

thomasmanke commented Oct 31, 2024

The multiqc_data group is not properly chnaged. This seems to have started with snakePipe3.1.0/multiqc1.25

@thomasmanke thomasmanke added the question Further information is requested label Nov 9, 2024
@thomasmanke
Copy link
Contributor Author

I have tested that with multiqc 1.25.1 the files in multiqc_data/ really get different group ownership:
The following files do not inherit the group defined at the periphery (-s)

  • multiqc_citations.txt
  • multiqc_data.json
  • multiqc_sources.txt
    Notably these are all files that are created by multiqc directly at the target location.
    All other files in multiqc_data/ are first created in some /tmp directory and then copied.

Suggestion: enforce compression of multiqc_data with 'multiqc --zip-data-dir'
Minor savings in storage, but this should fix most of the recent grp warnings.

Question: is the uncompressed multiqc_data used by anyone/any tool?

@thomasmanke
Copy link
Contributor Author

Of course the suggested solution is on snakePipe side, rather than BRB. So opened issue there too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants