search

Xiyachen / support-tools

Automatically exported from code.google.com/p/support-tools
Apache License 2.0
0 stars 0 forks source link

github_issue_converter.py outputs a RuntimeError: Unable to find Google Code issue #21 #90

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I'd like to port http://code.google.com/p/ibus to http://github.com/ibus/ibus.

When I run github_issue_converter.py, I got an error.

% python github_issue_converter.py --github_owner_username=ibus \
  --github_repo_name=ibus \
  --issue_file_path=$FILE/GoogleCodeProjectHosting.json \
  --project_name=ibus \
  --github_oauth_token=$TOKEN --rate_limit=false

Traceback (most recent call last):
  File "github_issue_converter.py", line 479, in <module>
    main(sys.argv)
  File "github_issue_converter.py", line 475, in main
    parsed_args.rate_limit)
  File "github_issue_converter.py", line 431, in ExportIssues
    issue_exporter.Start()
  File "support-tools/googlecode-issues-exporter/issues.py",
line 614, in Start
    self._AssertInGoodState()
  File "support-tools/googlecode-issues-exporter/issues.py",
line 683, in _AssertInGoodState
    last_gh_issue_id, last_gh_issue["title"]))
RuntimeError: Unable to find Google Code issue #21 'Fixed a typo in IMdkit.h'.
    Were issues added to GitHub since last export attempt?

It seems the command refers https://github.com/ibus/ibus/pull/21 but ibus has 
no issues.

Original issue reported on code.google.com by takao.fujiwara1 on 1 May 2015 at 10:17

GoogleCodeExporter commented 9 years ago 
When the GitHub Issue Exporter starts, it first queries the GitHub project to 
see if it already has any issues. (In case the exporter crashed/failed on a 
previous run.)

That particularly error comes from here:
https://code.google.com/p/support-tools/source/browse/googlecode-issues-exporter
/issues.py#680

It looks like it is trying to find the latest GitHub issue (#21 "fixed a typeo 
in IMdkit.h") in the Google Code issues dump, but not finding it.

This means that a GitHub issue was added since the previous export attempt, 
which would cause all of the issue numbers to be out of sync.

The fact that the project already has no issues is pretty suspicious. Could you 
try running the tool and attaching the entire command-line output as a TEXT 
file to this bug? I'd be curious to see what the rest of the logging out put 
said.

Original comment by chrsm...@google.com on 4 May 2015 at 6:41

GoogleCodeExporter commented 9 years ago 
> It looks like it is trying to find the latest GitHub issue (#21 "fixed a 
typeo in IMdkit.h") in the Google Code issues dump, but not finding it.

As I explained, it refers the pull requests 
https://github.com/ibus/ibus/pull/21 instead of issues.

There is no other logging:

% python github_issue_converter.py --github_owner_username=ibus \
  --github_repo_name=ibus \
  --issue_file_path=$JSON_PATH/GoogleCodeProjectHosting.json \
  --project_name=ibus \
  --github_oauth_token=$TOKEN --rate_limit=false
Getting any previously added issues...
Starting issue export for 'ibus'
Existing issues detected for the repo. Likely due to a previous
    run being aborted or killed. Checking consistency...
Traceback (most recent call last):
  File "github_issue_converter.py", line 479, in <module>
    main(sys.argv)
  File "github_issue_converter.py", line 475, in main
    parsed_args.rate_limit)
  File "github_issue_converter.py", line 431, in ExportIssues
    issue_exporter.Start()
  File "googlecode-issues-exporter/issues.py", line 614, in Start
    self._AssertInGoodState()
  File "googlecode-issues-exporter/issues.py", line 683, in _AssertInGoodState
    last_gh_issue_id, last_gh_issue["title"]))
RuntimeError: Unable to find Google Code issue #21 'Fixed a typo in IMdkit.h'.
    Were issues added to GitHub since last export attempt?

Original comment by takao.fujiwara1 on 4 May 2015 at 7:21