-
Notifications
You must be signed in to change notification settings - Fork 56
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
Crash after migrating a few issues #27
Comments
It looks like that this problem occurs only on machines with a fast internet connection. No Problems at home (down 16MB, up 640KB), same problem when running this script from a 100MB/100MB connection. Edit: No, it has nothing to do with the connection. |
Oh, and this repository is dead. Check the forks under the Network tab for more recent versions. |
Ah hadn't thought of looking at the forks, thanks! Too bad people abandon their projects like this. :-\ |
I don't like it either. I asked Arthur to at least write a quick note into the README. It was obviously asked too much. He also did not pull my quick fixes. Check the forks, find one you like and contribute to that, if you feel like it. |
@eXpl0it3r you also could check my fork. No guarantee, but I think my fork does not produce duplicates. At least, not that I remember :) |
I already starred your fork, so I can easily find it again, but I don't have the time to working with it, so I will certainly check it out later. ;) |
So I've been trying to move all the issues from the official Box2D Google Code project to GitHub, but for some reason it always fails with the
Bad credentials
exception.Since it works for x numbers of issues and only then errors out, it's definitely not a problem of my credentials and my guess would rather be, that the GitHub API blocks after a certain amount of calls, but I've no experience in that area.
Here's the output:
Restarting it again mostly leads to duplication of issues and since it never really finishes (never reached issue 302), I basically can't migrate everything.
Does anyone know if there's some API limitation that errors out with
Bad credentials
or see where the error might originate from otherwise?Besides that, it would be great if one could specify an issue number, from where the script should start from copying, since it takes quite a bit to skip over one issue.
The text was updated successfully, but these errors were encountered: