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
Version 0.6.0 reuploaded ? #228
Comments
Yes, unfortunately this was done by mistake on our side (#135). We hope it never happens again. Closing now, feel free to follow with further questions. 👍 |
Thanks @nicoddemus not to pick on you but just to confirm as I did notice the linked issue before reporting, the linked issue is from Apr 2018, however this hash change I mentioned is more recent, so did you refer to the earlier issue just to share that the reason is same as the earlier hash change? |
Oh sorry about that. Weird, no, I'm not aware of this happening again recently. @goodboy do you have any inputs here? |
Ah, digging further in previous successful build: https://travis-ci.org/linkedin/qark/jobs/557908230#L479
So it might indeed be the same issue. I am going to update the hash to Thanks @nicoddemus |
It looks like hashes for the
0.6.0
wheel have been updated however I still see the old date at https://pypi.org/project/pluggy/0.6.0/#modal-close (15 Apr 2018)New hash (py2):
d345c8fe681115900d6da8d048ba67c25df42973bda370783cd58826442dcd7c
Old hash:
7f8ae7f5bdf75671a718d2daf0a64b7885f74510bcd98b1a0bb420eb9a9d0cff
Is this expected?
I just noticed it as it led to failure of one of my recent PR's tests.
Successful tests with same pluggy version in requirements file 28 days ago: https://travis-ci.org/linkedin/qark/jobs/557908230
Failure today: https://travis-ci.org/linkedin/qark/jobs/569709745
Thanks!
The text was updated successfully, but these errors were encountered: