On docker, we have
/tmp/bedtools/pybedtools.5wq011d4.tmp: ISO-8859 text
and the offending line is composed on non-readable characters (bytes)
Locally, we have
pybedtools.br03fzlu.tmp: ASCII text
and the line is text.
So reading and processing the sequence e.g. /data/assembly/Homo_sapiens/GRCh38/Homo_sapiens.GRCh38.dna.chromosome.2.fa.gz seems to be done differently, as if pybedtools behaves differently in reading/writing files?!?
Aims/objectives.
Reading the sequencing context works fine locally (development), but fails with
on production. This happens here: https://github.com/dieterich-lab/scimodom/blob/d297d0eb43b2b08c10452b4cb946b6c6304c4adc/server/src/scimodom/services/file.py#L489
On docker, we have /tmp/bedtools/pybedtools.5wq011d4.tmp: ISO-8859 text and the offending line is composed on non-readable characters (bytes)
Locally, we have pybedtools.br03fzlu.tmp: ASCII text and the line is text.
So reading and processing the sequence e.g. /data/assembly/Homo_sapiens/GRCh38/Homo_sapiens.GRCh38.dna.chromosome.2.fa.gz seems to be done differently, as if pybedtools behaves differently in reading/writing files?!?
A clear and concise description of todo items.
We need a working sequence context.