-
Notifications
You must be signed in to change notification settings - Fork 10
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
Parsing bug in oscar.pyx #45
Comments
Here's a more precise example:
prints
because (BTW, the commit is also not in github. https://api.github.com/repos/buttermilk-crypto/b2/commits/39fdb9fa930fcac4a182b3e4d29190c0f436c925 does not appear, even though it is returned by |
Content of some commits associated with a project may be lost and the current repo may no longer have them: hence no way to recover it Yes, the instantiation of commits for which only sha1 is available need to be done more gracefully: such commits will always be there as there is often no way to recover lost content Doing this may need nontrivial design decisions: do you have a suggestion? |
I'm going to look into this on the weekend. The goal is to catch these cases and use information from other relations that we have, e.g. to retrieve parents, author etc., and remove reasonable defaults (blank strings / special values) for the rest. |
New oscar.pyx changes may be triggering some parsing bugs. The following code, run on da4:
Produces a few correct responses, then a parse error:
The problem appears to be in line 1056 of the Commit class; this sometimes doesn't work, and it appears that maybe self.data is returning an empty string in some cases:
The text was updated successfully, but these errors were encountered: