Closed lawremi closed 4 years ago
Should be fixed in GenomeInfoDb 1.23.14 (see commit 573077ce).
A static copy would be faster but would become out-of-sync when the genome changes, like here. So we would need to have some mechanism in place to alert us when this happens e.g. some long tests (they're run once a week) that pull the sequence information again from UCSC and compare to the static copy.
Thanks. That the genome can change is problematic from the reproducibility standpoint. We may want to ensure stability, i.e., be purposefully out of sync, and only update once a release or something, with the information tied to the package version.
The HelloRanges package is failing in devel and release because the dynamic resolution of sequence information from UCSC is broken for hg19:
I wonder if it would be better to include a static copy of this information, at least for the most commonly accessed genome? Stabler, faster and more reproducible.