Closed fedarko closed 1 year ago
ok, pinning bcftools didn't work. but from the latest logs, i can see the version of pysam being installed -- looks like it's pysam-0.11.2.2
???? this is a really old version, so it makes sense that it could be causing these problems. why is it getting installed, tho.
tried upping the lower pysam pin to 0.15; we'll see what happens. (looks like pysam 0.15.2, etc are still on bioconda -- https://anaconda.org/bioconda/pysam/files -- so idk why conda is deciding to install this ancient pysam version.)
alright, that fixed it??? not gonna look a gift horse in the mouth.
Looks like all the tests that import pysam give this sort of error:
And importing pysamstats also breaks things, but in a different way:
Not sure what's up exactly -- the GitHub Actions logs are being weirdly vague about what versions of pysam/pysamstats were installed (they say
... (more hidden) ...
where i would expect to see info about these versions ._.) It looks like GitHub Actions is installing a relatively new version of bcftools (v1.17), and it looks like bcftools has conflicted with pysam before in a way that cause a similar libhts ImportError (https://github.com/pysam-developers/pysam/issues/427) -- maybe try pinning bcftools to < 1.16?