-
Updated
Jul 31, 2021 - Java
workflow-management
Here are 96 public repositories matching this topic...
-
Updated
Jul 12, 2021 - Shell
Snakemake version
5.27.4
Describe the bug
When using a pathlib Path object to specify a conda envronment snakemake errors out. Log is below. Converting the Path object to a string serves as a workaround, however I know pathlib support has been extended lately and this seems like something that was missed.
Logs
AttributeError in line 31 of /path/to/my/file.smk:
'Po
Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).
To Reproduce
odin deploy -f test.job.yamlodin log -i {job_id}
vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]
goroutine
-
Updated
Jun 1, 2021 - Python
-
Updated
Jul 31, 2021 - C#
-
Updated
Apr 24, 2018 - JavaScript
-
Updated
Nov 3, 2020 - Go
-
Updated
Jul 30, 2021 - Python
-
Updated
Jun 28, 2021 - Python
-
Updated
Feb 2, 2021 - Go
-
Updated
Apr 23, 2021 - Haskell
-
Updated
Jul 12, 2021 - Python
-
Updated
Aug 29, 2014 - Python
-
Updated
Apr 14, 2020 - JavaScript
-
Updated
Apr 8, 2021 - Java
-
Updated
Jul 31, 2021 - Java
-
Updated
Jul 10, 2019 - Python
-
Updated
Jul 27, 2021 - PHP
-
Updated
Nov 8, 2018 - JavaScript
-
Updated
Feb 2, 2021 - PHP
-
Updated
Jul 15, 2021 - JavaScript
-
Updated
Mar 2, 2020 - JavaScript
-
Updated
Jan 2, 2018 - Python
-
Updated
Jul 30, 2021 - Go
-
Updated
Jul 15, 2021 - JavaScript
-
Updated
Jul 20, 2021 - Go
Improve this page
Add a description, image, and links to the workflow-management topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the workflow-management topic, visit your repo's landing page and select "manage topics."
Is your feature request related to a problem? Please describe.
There is an optional config for namespace called "sampled retention days" that can be specified when create a namespace. It was created long ago as workaround for long retentions before long term archival was available.
Describe the solution you'd like
We should get rid of the sampled retention.
**Describe alternatives