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
from_data to dtype=2 #44
Conversation
This pull request introduces 1 alert when merging 840eb60 into bcc7a28 - view on LGTM.com new alerts:
Comment posted by LGTM.com |
Can you rebase this for the history? |
Didn't mean for this to supersede #42, unless you're confident it's harmless to downstream. Which do you want to proceed with? |
It isn't completely harmless downstream as hashes change, but we need it in to start computing I think. |
ok, rebased. clean pass locally, so clear for rev/merge after CI |
This pull request introduces 1 alert when merging 729493a into bcc7a28 - view on LGTM.com new alerts:
Comment posted by LGTM.com |
… removing too much data
This pull request introduces 1 alert when merging ac3a292 into 1dfc906 - view on LGTM.com new alerts:
Comment posted by LGTM.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
(1 commit)
could cause problems downstream
needs rebase after #42 merged