Closed jsstevenson closed 3 months ago
it appears that something about the dependency resolver in the most recent pipenv release was changed -- pinning the last prior release fixes: https://github.com/cancervariants/metakb/actions/runs/9453887874/job/26040206194?pr=351
that's not a fix, though, because we want to mirror elastic beanstalk behavior, and chances are it means we're doing something wrong
Also, I'm not able to reproduce this locally, so maybe it's not a big deal (but also this is very uncool)
Closed by #351.
Got a surprising test failure in a recent PR, so I re-ran a commit that had previously passed (HEAD on
staging
). And it failed: https://github.com/cancervariants/metakb/actions/runs/9384230431/job/26039271279The stated error relates to gene-normalizer requirements conflicts, but it's also possible that it's something upstream of that.