David Laehnemann

Hi @tomtung, the flame crate approach is very useful when flamegraphing specific parts of code. But having to explicitly mark functions for tracking can be prohibitive. Especially when working with...

Jep, definitely. There are use cases for both. I did expect `rust-unmangle` to become unnecesaary at some point, as Rust name mangling evolves, just still saw some function calls that...

I can only second this. Any extra context information when debugging input would be great. Might have also helped isolating this bug that I found and reported over in issue...

This e.g. happens, if a `skip: True #[osx)` has a typo in the brackets and the linux test is also short-circuited. I also posted this over at: https://github.com/bioconda/bioconda-utils/issues/349#issuecomment-458902538

Just converted this to a draft, so that it doesn't accidentally get merged. Hope that's OK.

BTW, the option to do this is a small (cliackable) sentence right under the reviewer suggestions. Took me a while to find it, when I first went looking for it....

Can you try downgrading the `python` in your `snakemake` environment to `3.11`? Python does not follow semantic versioning and a lot of things broke in the step from `3.11` to...

I was on the wrong track initially, but have now looked into it. This should be fixed with #76 and if you upgrade to the latest release of the workflow,...

The `Traceback` and the `TypeError` actually point to the problem: The function `get_contigs()` in line 44 of `common.smk` uses the `pandas` function `read_table()` with the argument `squeeze=True`: https://github.com/snakemake-workflows/dna-seq-gatk-variant-calling/blob/cffa77a9634801152971448bd41d0687cf765723/workflow/rules/common.smk#L44 As the...

No worries about the formatting, it's not always clear where and how to find info such as the docs for the GitHub Markdown syntax. And you definitely provided all the...