Skip to content

Improve reliability of issue migration #88

@GoogleCodeExporter

Description

@GoogleCodeExporter
There have been a lot of issues reported about migrations failing due to failed 
issue migrations. Dumping all of those to this master issue.

The underlying problem is due to underlying problems in App Engine's urlfetch 
API, and the fact that the Google Code Exporter aborts the migration if any 
GitHub API calls fail. A 0.01% chance of failure across hundreds of issues, 
across dozens of comments is a serious problem.

If you delete the GitHub repository and try again, there is a chance it will 
work on the next try. We've been making small progress towards reliability 
here; but the real fix is to retry GitHub API calls in the event of failure. 
(And check if state changing requests like POSTs actually went through.)


Original issue reported on code.google.com by chrsm...@google.com on 24 Apr 2015 at 10:20

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions