-
Notifications
You must be signed in to change notification settings - Fork 21
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
v2.0.0-beta.3 run: failed to find loop device, then --resume results in Failed to invoke observer completion handler (NullPointerException in BcoRenderer) #362
Comments
I reran pgsc_calc with --resume after a loop device error and got this:
|
I ran the exact command that was in .command.sh, and it succeeded without an error:
The original loop devices error happens with and without this recommendation: #361 (comment), and on both 64 and 32 GB of RAM, and also with either 65 or 93 scorefiles. |
Hmmm, we might have to investigate this further. It could also be some interaction with how singularity was initially set up/administered. You could also try conda to see if that works? |
I will look into conda. The loop devices themselves look normal. Perhaps it is some setup issue that occurs under certain conditions, since I previously used the same setup without seeing this error. |
I can still replicate the error but I don't think it's the root cause of the pipeline failing to run:
|
Does the problem still happen if you set: Lines 306 to 313 in 96fbb23
to |
I'll try that next, thanks. The loop device might be a different issue since I got this error without the loop device message:
command.sh:
This part isn't a critical error since all of the data and results are still present. |
This time, running the same pipeline, I got this error without the BcoRenderer issue. I would usually be able to provide more informative information but it seems like I can't fully reproduce the exact error each time despite having a very similar or exactly the same setup, for some reason.
.command.run:
.command.sh:
In the work directory, there is this file: pgsc_1000G_v1.tar.zst. (Also, I'm not able to get Conda working in the environment. I'm running the newest release of pgsc_calc with Singularity. I run 1 VCF file at a time. Between different VCFs, this error does not always happen, but it happened on a large percentage of runs/files (four out of five runs). However, I'm not sure that the files are the issue since I remember that some of the files completed without this error on other runs yesterday.) |
I switched to enabled = false, but it still crashes almost always with the loop devices issue. The last running process on four of the times I got the loop device error was: For the above 4 cases, the nextflow logs show if failed on: PGSCATALOG_PGSCCALC:PGSCCALC:ANCESTRY_PROJECT:EXTRACT_DATABASE, for pgscatalog-comb, pgscatalog-comb PGSCATALOG_PGSCCALC:PGSCCALC:MAKE_COMPATIBLE:PLINK2_VCF for pgscatalog-rela PGSCATALOG_PGSCCALC:PGSCCALC:ANCESTRY_PROJECT:EXTRACT_DATABASE for plink2 Here are some excerpts from the work directory command.run files:
|
Description of the bug
I ran the current version of pgsc_calc with 63 scorefiles on a single sample and got this error:
I re-ran pgsc_calc with the --resume flag, and it seemed to work (correctly generated the _pgs.txt.gz file), but also it had this strange error:
It says there was an error when trying to render the BioCompute Object (BCO), as indicated by the NullPointerException in the BcoRenderer, which I haven't heard of.
Do you have any ideas about what could be causing this? It is odd that resuming with no other changes works, but it doesn't work on its own the first try. I replicated this on another machine with a different sample file.
Command used and terminal output
Relevant files
No response
System information
Nextflow version: 24.04.4 build 5917
System: Linux 6.5.0-1022-aws
Runtime: Groovy 4.0.21 on OpenJDK 64-Bit Server VM 11.0.24+8-post-linux-1linux322.04
Encoding: UTF-8 (ANSI_X3.4-1968)
CPUs: 8 - Mem: 62.1 GB (8.9 GB) - Swap: 0 (0)
"/home/linux/urunner/system/test/file10001_filestudy_yearofsample_unknown_sex_unknown.e_output/samplesheet.csv", "format": "csv",
"scorefile": "/home/linux/urunner/system/test/custom_scores/*.txt.gz", "pgs_id": null, "trait_efo": null,
"efo_id": null,
"pgp_id": null,
"efo_direct": false,
"run_ancestry": "/home/linux/urunner/data/pgsc_1000G_v1.tar.zst",
"ancestry_checksums": "/home/linux/urunner/tools/pgsc_calc/assets/ancestry/checksums.txt",
"hg19_chain": null,
"hg38_chain": null,
"load_afreq": true,
"geno_ref": 0.1,
"mind_ref": 0.1,
"maf_ref": 0.05,
"hwe_ref": 0.0001,
"indep_pairwise_ref": "1000 50 0.05",
"ld_grch37": "/home/linux/urunner/tools/pgsc_calc/assets/ancestry/high-LD-regions-hg19-GRCh37.txt",
"ld_grch38": "/home/linux/urunner/tools/pgsc_calc/assets/ancestry/high-LD-regions-hg38-GRCh38.txt",
"ref_format_version": "v0.1",
"ref_samplesheet": "/home/linux/urunner/tools/pgsc_calc/assets/ancestry/reference.csv",
"projection_method": "oadp",
"ancestry_method": "RandomForest",
"ref_label": "SuperPop",
"n_popcomp": 5,
"normalization_method": "empirical mean mean+var",
"n_normalization": 4,
"pca_maf_target": 0.0,
"pca_geno_miss_target": 0.1,
"liftover": false,
"target_build": "GRCh37",
"min_lift": 0.95,
"min_overlap": 0.0,
"keep_ambiguous": false,
"keep_multiallelic": false,
"copy_genomes": false,
"genotypes_cache": "/home/linux/urunner/system/test/cache",
"only_bootstrap": false,
"only_input": false,
"only_compatible": false,
"only_match": false,
"only_projection": false,
"only_score": false,
"skip_ancestry": true,
"outdir": "/home/linux/urunner/system/test/results",
"publish_dir_mode": "copy",
"email": null,
"email_on_fail": null,
"plaintext_email": false,
"monochrome_logs": false,
"hook_url": null,
"help": false,
"version": false,
"config_profile_name": null,
"config_profile_description": null,
"custom_config_version": "master",
"resume": true,
"custom_config_base": "https://raw.githubusercontent.com/nf-core/configs/master",
"config_profile_contact": null,
"config_profile_url": null,
"max_memory": "62.GB",
"max_cpus": 8,
"max_time": "240.h"
The text was updated successfully, but these errors were encountered: