Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / fulcrumgenomics/dagr issues and pull requests
#379 - Bugfix/nested non unit tasks
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#379 - Bugfix/nested non unit tasks
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#379 - Bugfix/nested non unit tasks
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#379 - Bugfix/nested non unit tasks
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#378 - Add VarDictJava's experimental --fisher option to VarDictJavaEndToEnd
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#378 - Add VarDictJava's experimental --fisher option to VarDictJavaEndToEnd
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#378 - Add VarDictJava's experimental --fisher option to VarDictJavaEndToEnd
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#378 - Add VarDictJava's experimental --fisher option to VarDictJavaEndToEnd
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#378 - Add VarDictJava's experimental --fisher option to VarDictJavaEndToEnd
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#377 - CPU and memory resource detection should be Docker container aware.
Issue -
State: open - Opened by jacarey over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#376 - Add withPrefix and withSuffix to Pipeline
Pull Request -
State: closed - Opened by mjhipp over 4 years ago
- 1 comment
#375 - Adding a pipeline to parse dagr execution reports.
Pull Request -
State: open - Opened by nh13 over 4 years ago
#375 - Adding a pipeline to parse dagr execution reports.
Pull Request -
State: open - Opened by nh13 over 4 years ago
#375 - Adding a pipeline to parse dagr execution reports.
Pull Request -
State: open - Opened by nh13 over 4 years ago
#374 - ResourceSet bug when subsetting resources and some performance optimizations
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#374 - ResourceSet bug when subsetting resources and some performance optimizations
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#374 - ResourceSet bug when subsetting resources and some performance optimizations
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#374 - ResourceSet bug when subsetting resources and some performance optimizations
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#374 - ResourceSet bug when subsetting resources and some performance optimizations
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#374 - ResourceSet bug when subsetting resources and some performance optimizations
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#373 - Various Task Manage Speedups
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#373 - Various Task Manage Speedups
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#373 - Various Task Manage Speedups
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#373 - Various Task Manage Speedups
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#373 - Various Task Manage Speedups
Pull Request -
State: closed - Opened by nh13 over 4 years ago
- 1 comment
#372 - Add the "-K" option from bwa
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#372 - Add the "-K" option from bwa
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#372 - Add the "-K" option from bwa
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#372 - Add the "-K" option from bwa
Pull Request -
State: closed - Opened by nh13 over 4 years ago
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#371 - API should not allow mixins between VariableResources and FixedResources
Issue -
State: open - Opened by clintval over 4 years ago
- 3 comments
Labels: bug
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#370 - Why does Dagr use the physical processor count instead of logical for Macs only?
Issue -
State: closed - Opened by clintval over 4 years ago
- 1 comment
Labels: question
#369 - Use Files.deleteIfExists() in `DeleteBam` rather than `paths.filter(F…
Pull Request -
State: closed - Opened by tfenne almost 5 years ago
#369 - Use Files.deleteIfExists() in `DeleteBam` rather than `paths.filter(F…
Pull Request -
State: closed - Opened by tfenne almost 5 years ago
#369 - Use Files.deleteIfExists() in `DeleteBam` rather than `paths.filter(F…
Pull Request -
State: closed - Opened by tfenne almost 5 years ago
#369 - Use Files.deleteIfExists() in `DeleteBam` rather than `paths.filter(F…
Pull Request -
State: closed - Opened by tfenne almost 5 years ago
#369 - Use Files.deleteIfExists() in `DeleteBam` rather than `paths.filter(F…
Pull Request -
State: closed - Opened by tfenne almost 5 years ago
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#368 - PicardTask to use the Intel inflater/deflater only if it is safe, by default
Pull Request -
State: closed - Opened by clintval almost 5 years ago
- 5 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#367 - PicardTask to allow overriding default use of JDK inflater
Pull Request -
State: closed - Opened by clintval about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#366 - Add CorrectUmis to dagr tasks
Pull Request -
State: closed - Opened by gpratt about 5 years ago
- 2 comments
#365 - Attempt to make the GATK tasks a) auto-detect GATK version and b) swi…
Pull Request -
State: closed - Opened by tfenne about 5 years ago
- 4 comments
#365 - Attempt to make the GATK tasks a) auto-detect GATK version and b) swi…
Pull Request -
State: closed - Opened by tfenne about 5 years ago
- 4 comments
#365 - Attempt to make the GATK tasks a) auto-detect GATK version and b) swi…
Pull Request -
State: closed - Opened by tfenne about 5 years ago
- 4 comments
#365 - Attempt to make the GATK tasks a) auto-detect GATK version and b) swi…
Pull Request -
State: closed - Opened by tfenne about 5 years ago
- 4 comments
#365 - Attempt to make the GATK tasks a) auto-detect GATK version and b) swi…
Pull Request -
State: closed - Opened by tfenne about 5 years ago
- 4 comments