New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] unit-tests started failing on github #1959
Labels
Comments
Another issue is h5py which just had a major version change yesterday to 3.0.0.
|
bmccandless
pushed a commit
that referenced
this issue
Oct 31, 2020
h5py recently changes and now values once returned as str are now returned as bytes. This would have caused a much larger change, so instead the version is restricted to <3.0.0. This caused the bulk of the testing failues. A few other changes were needed to make a few other tests pass. #1959
bmccandless
pushed a commit
that referenced
this issue
Nov 1, 2020
* Updates due dependency version changes. h5py recently changes and now values once returned as str are now returned as bytes. This would have caused a much larger change, so instead the version is restricted to <3.0.0. This caused the bulk of the testing failues. A few other changes were needed to make a few other tests pass. #1959
seve
added a commit
that referenced
this issue
Nov 5, 2020
* Updates due dependency version changes. h5py recently changes and now values once returned as str are now returned as bytes. This would have caused a much larger change, so instead the version is restricted to <3.0.0. This caused the bulk of the testing failues. A few other changes were needed to make a few other tests pass. #1959
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Several tests started failing yesterday.
To Reproduce
This can be reproduced by cloning cellxgene in a new virtual environment, building and running.
Additional context
There a few possible issues. semver and numpy recently upgraded.
and pip may have just changed how it resolves dependency conflict.
So far I'm able to work through the issues with minor code changes.
The text was updated successfully, but these errors were encountered: