clkao / support-tools Goto Github PK

What steps will reproduce the problem?
1.trying to export jbrout project to my GitHub account
2.
3.

What is the expected output? What do you see instead?
expecting: something nice (not sure exactly), export should finish without 
problems
observing:

Aw, Snap!

There was an error migrating the project to GitHub.

The error is as follows:

Error getting GitHub user.

You can try to export the project again, read our FAQ for any known issues, or 
contact Google for assistance.


What version of the product are you using? On what operating system?
NA

Please provide any additional information below.

[deleted issue]

The --project_name flag appears to be required, but is not mentioned in 
GitHubIssueImporter?

What steps will reproduce the problem?
1. run the github_issue_converter.py migration tool
2. in the middle of transferring comments, abort the script. In my case it was 
aborted due to the abuse filter kicking in.
3. run the github_issue_converter.py migration tool once more

What is the expected output? What do you see instead?
Expected that the tool picked up where it left of by continuing the migration 
of not yet transferred comments. But instead it skips this issue completely and 
continues with the next.

What version of the product are you using? On what operating system?
Linux *** 3.13.0-43-generic #72~precise1-Ubuntu SMP Tue Dec 9 12:14:18 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

Branch name: development-oud

Purpose of code changes on this branch:

Updated comments and added naming discrepancy notice to module docstring.

After the review, I'll merge this branch into:
/trunk

python3 googlecode-issues-exporter/github_issue_converter.py <a lot of options>
  File "googlecode-issues-exporter/github_issue_converter.py", line 423
    print "\nDone!\n"
                    ^
SyntaxError: Missing parentheses in call to 'print'

---

Reported on google-code-shutdown@

Branch name: development-oud

Purpose of code changes on this branch:
Applied gpylint style changes.

Please see in-line comments.

After the review, I'll merge this branch into:
/trunk

What steps will reproduce the problem?
1. Use the 'Export to GitHub' tool

Old wiki at:
https://code.google.com/p/skype4pidgin/w/list

Not showing at:
https://github.com/EionRobb/skype4pidgin/wiki

What steps will reproduce the problem?
1. Run the https://code.google.com/export-to-github/ export

What is the expected output? What do you see instead?
Expect to see issues copied, nothing has happened

Old issues list:
https://code.google.com/p/skype4pidgin/issues/list

Nothing at:
https://github.com/EionRobb/skype4pidgin/issues

The issue exporter script takes both a github user token and a username, when 
the username can be derived from the token by looking up the current user's 
information (https://developer.github.com/v3/users/#get-the-authenticated-user)

This would leave one less option for the user to specify and would simplify 
logic to guarantee that the current user is the user they claim to be.

Looks like eclipselabs projects 
(https://code.google.com/a/eclipselabs.org/hosting/) can't be exported - I only 
get an error "Error getting project <name>" after trying to use "Export to 
Github->Start Export" button.

Example project: https://code.google.com/a/eclipselabs.org/p/plugindependencies/

What steps will reproduce the problem?
1. run wiki2gfm.py with wiki input from 
https://code.google.com/p/fusioncatcher/wiki/Manual 

What is the expected output? What do you see instead?

It is expected to end without error. The following error is shown:


Warning (line 1 of input file):
A summary pragma was used for this wiki:
    Manual
Consider moving it to an introductory paragraph.

Warning (line 3 of input file):
A table of contents plugin was used for this wiki:
    <wiki:toc max_depth="2" />
The Gollum wiki system supports table of content generation.
See https://github.com/gollum/gollum/wiki for more information.
It has been removed.

Traceback (most recent call last):
  File "/apps/bin/support-tools/wiki_to_md/wiki2gfm.py", line 122, in <module>
    main(sys.argv)
  File "/apps/bin/support-tools/wiki_to_md/wiki2gfm.py", line 118, in main
    converter.Convert(input_stream, output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 123, in Convert
    input_line = self._ProcessBody(input_line, input_lines, output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 215, in _ProcessBody
    output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 346, in _ProcessLine
    output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 513, in _ProcessMatch
    handler(input_line, match, output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 604, in _HandleBold
    self._HandleTag(input_line, "Bold", output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 1281, in _HandleTag
    self._CloseTag(input_line, tag, output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/converter.py", line 433, in _CloseTag
    handler(input_line, output_stream)
  File "/apps/bin/support-tools/wiki_to_md/impl/formatting_handler.py", line 297, in HandleBoldClose
    self._HandleFormatClose(input_line, output_stream, "Bold")
  File "/apps/bin/support-tools/wiki_to_md/impl/formatting_handler.py", line 960, in _HandleFormatClose
    self._Write("{0}{1}{0}".format(tag, format_buffer), output_stream)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2013' in position 
54: ordinal not in range(128)

Provide a way for project admins to remove the "Export to GitHub" button.

So everyone can see it, this is a copy of 
https://code.google.com/p/support/issues/detail?id=33898.

What steps will reproduce the problem?
Step 1. Move a project using the "Project moved" button at 
https://code.google.com/p/mmisw/adminAdvanced
Step 2. Click on the "Publish project" button, which then appears, presumably 
to 'unmove' the forward link ("All project contents will become visible to all 
users.")
Step 3. Try to access the project

What is the expected output? What do you see instead?
Rather than restoring access to the project as it was before, all access 
attempts (whether to the root path, or to the redirect path) result in a 
redirect failure. The URL is correct 
(https://code.google.com/hosting/moved?project=mmisw in my case) but the page 
shows 404 error.  
  If you then go back and hit the Project moved button, and enter an external URL, everything looks like after step 1 above -- people get a page linking forward.  If you enter an internal project name (mmisw), we're back to the 404 error.
  While we wee in 403/404 error mode, the contents within the project were visible to direct links (at least, seemed to be for a while; but no longer).


What browser (or git/hg/svn client) are you using? On what operating
system?
Chrome on Mac 10.9.

Please provide any additional information below.

This is a copy of https://code.google.com/p/support/issues/detail?id=33898.

We do still need access to the information in this project, and would not have 
done the move if we'd realized it was irreversible and effectively removed the 
project content.

The 404 error contains the following:

404. That’s an error.

The requested URL /hosting/moved?project=mmisw was not found on this server. 
That’s all we know.

I understand that the GitHubIssueImporter cannot create issues and comments as 
the original authors, but it would be nice if it would add a note in the 
content that stated who *actually* wrote it?

I plan to migrate a project from GoogleCode to Bitbucket. The main reason not 
choosing GitHub was it's issue handler doesn't support file attachments(just 
pictures). But Bitbucket does! The GoogleCodeProjectHosting.json file created 
by Takeout contains all necessary info to concatenate an attachment url ,so it 
would be nice to have a command line option to migrate file attachments of 
issue comments too.

It would be nice to know what could go wrong before doing the import and ending 
up with a half-way result. Here's some of the things I would have liked, in my 
experience trying out the GitHubIssueImporter tool.

I wanted to provide a username mapping, to keep as much of the information as 
possible, but it wasn't possible to know which mappings were even needed before 
starting? I modified the script to raise an exception in _GetIssueAssignee when 
a mapping is not found, instead of returning the --github_owner_username, 
adding entries to the mapping files as errors were found.

Issues can only be assigned to users that have commit access to the repository. 
If there was a dry-run mode, it would be nice if it could check whether that's 
the case, or at least, list the users that will be needed, so it can be 
verified that they have commit access ahead of time.

GitHub seems to reject empty comments, which causes some errors to appear 
during the importation.

My old hg project log are in Chinese:

    https://code.google.com/p/zhmakeindex/source/list

But in the new project

    https://github.com/Leo-Liu/zhmakeindex/commits/master

all the Chinese characters are ??? in the log.

Branch name: development-oud

Purpose of code changes on this branch (generate_user_map.py):
1. Added a tool to auto-generate a file users.json, which maps Google Code user 
to BitBucket user.

Example:

{
    "users": {
        "[email protected]": "oud-google",
        "oudavid86": "oudavid86"
    }
}

Please note that the user must change the right-side user, otherwise it will 
just default to the Google Code username.

2. Added a tool to convert issues data from Takeout into a format accepted by 
BitBucket (bitbucket_issue_converter.py).

I extracted the issues into a class GoogleCodeIssue and comments into 
GoogleCodeComment. These two classes can/should be shared with the GitHub issue 
importer. There are also two corresponding classes BitBucketIssue and 
BitBucketComment. Below is an example of the JSON that is generated from 
bitbucket_issue_converter.py.

Example:

{
    "comments": [
        {
            "content": "As the input size increases exponentially, we need to make sure that the algorithm isn't unnecessarily computing sums it doesn't need to.",
            "created_on": "2014-07-01T21:37:12.000Z",
            "id": 0,
            "issue": 1,
            "updated_on": "2014-07-01T21:37:12.000Z",
            "user": "oudavid86"
        },
        {
            "content": "Assigning issue to oudavid86.",
            "created_on": "2014-07-01T21:40:05.000Z",
            "id": 1,
            "issue": 1,
            "updated_on": "2014-07-01T21:40:05.000Z",
            "user": "oudavid86"
        }
    ],
    "issues": [
        {
            "assignee": "oudavid86",
            "content": "Need unit test to check that run-time complexity does not exceed O(N^2)",
            "content_updated_on": "2014-07-01T21:40:05.000Z",
            "created_on": "2014-07-01T21:37:12.000Z",
            "id": 1,
            "kind": "bug",
            "priority": "critical",
            "reporter": "oud-google",
            "status": "open",
            "title": "Need unit test to check that run-time complexity does not exceed O(N^2)",
            "updated_on": "2014-07-01T21:37:12.000Z"
        }
    ],
    "meta": {
        "default_kind": "task"
    }
}

A user can take this json, zip it up with attachments (if any), and import them 
into BitBucket here: 
https://bitbucket.org/<USER>/<PROJECT>/admin/issues/import-export

After the review, I'll merge this branch into:
/trunk

Branch name: development-oud

Purpose of code changes on this branch:
Fixed naming discrepancies and style issues.

After the review, I'll merge this branch into:
/trunk

What steps will reproduce the problem?
Attempt to export https://code.google.com/p/ftpii/ to 
https://github.com/joedj/ftpii/

What is the expected output? What do you see instead?
Expected output is a successful project import.
Observed output is "There was an error importing commits" at 
https://import.github.com/joedj/ftpii/import