Currently, the IGV reporting directory tries to keep all the resource files within it to make the directory self-contained. It does so through the includeInputs mechanism, but it is not clear whether they are supposed to be symlinks or copies. If they are copies, then it is duplication without much added benefit. If it is symlinks, then it is not clear if all systems will support symlinks.
For us, when using Google Cloud Batch executor with Fusion enabled, the files seem to be broken. There are other reports of similar behavior and they are claimed to have been fixed, but we don't see the fix in the latest version.
Nextflow version: 24.04.3 build 5916
Hardware: GCP VM n2-standard-16
Executor: Google Cloud Batch
Container Engine: Docker
OS: Ubuntu Linux 22.04
Version of nf-core/cutandrun: master (v3.2.2)
Description of the bug
Currently, the IGV reporting directory tries to keep all the resource files within it to make the directory self-contained. It does so through the
includeInputs
mechanism, but it is not clear whether they are supposed to be symlinks or copies. If they are copies, then it is duplication without much added benefit. If it is symlinks, then it is not clear if all systems will support symlinks.For us, when using Google Cloud Batch executor with Fusion enabled, the files seem to be broken. There are other reports of similar behavior and they are claimed to have been fixed, but we don't see the fix in the latest version.
Command used and terminal output
Relevant files
No response
System information
Nextflow version: 24.04.3 build 5916 Hardware: GCP VM n2-standard-16 Executor: Google Cloud Batch Container Engine: Docker OS: Ubuntu Linux 22.04 Version of nf-core/cutandrun: master (v3.2.2)