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
KeyError: 'sha1' #19
Comments
Now that's a trick. The API is not returning a sha1, but we'd like to be able to detect a revert. This means that we might just give up on detecting a revert for this revision. We might also try to go to the API to look for content so we can generate our own sha1. |
Weird, the API is returning the sha1 when I make a request on Special:ApiSandbox: |
The page 40677 contains the revision 40327912, which has an attribute reverts.api.check_rev(session, {'revid':40679748,'pageid':40677}, radius=7) but it happens when I increase the radius to 8: reverts.api.check_rev(session, {'revid':40679748,'pageid':40677}, radius=8) Using a big radius should not be a reason for failure, because 40679748 was reverted by the revision which is right after it in the history (40686393), and a radius of 2 is enough to detect that (BTW: shouldn't it radius 1 be enough too?). In other words, we have something like this: |
Fixed in a293667 And updated in v0.4.11 |
works fine, however
causes the following error:
The text was updated successfully, but these errors were encountered: