"Error creating new issue: NullError: Cannot call "ez" on null Close"

[titoBouzout]

When trying to move
sublimehq/sublime_text#160
to
SublimeTextBugs/DefaultPackages

I got this red error:
"Error creating new issue: NullError: Cannot call "ez" on null Close"

When I tried to add the bug to this repo, "github-issue-mover" I also got this message from github:
"There was an error creating your Issue: was submitted too quickly after a previous comment."

So probably my username has some kind of temporal block, because I moved many issues in a short time, could probably be a good idea to add a message somewhere "Your github account maybe temporally blocked"

[dcharbonnier]

same error for me but on the first try

[dcharbonnier]

https://github.com/jotweh/IssueRelocate works

[bootstraponline]

This is annoying. GitHub will block the account from making comments and you have to wait for hours for the temporary comment ban to expire. I think the issue mover could detect the 403 response and provide an intelligent error message.

[bootstraponline]

https://github.com/jotweh/IssueRelocate works

that works because it doesn't even attempt to copy comments according to the readme

"It does not copy the issue comments"

[bootstraponline]

The API docs explain a bit more about the rate limit.

• https://developer.github.com/v3/#abuse-rate-limits

[stal1n274]

I have the same error while trying to move an issue:

"Error creating new issue: NullError: Cannot call "ez" on null Close"

[ahundt]

I'm getting this same error, and I haven't made changes in a couple days so I don't think it is a rate limit problem.

[jgravois]

i think im experiencing the same error as @ahundt. personally, i used the tool successfully once in the past, but now immediately encounter the error when attempting to move an issue.

looking at github > settings > authorized applications i don't see the Issue Mover listed. i tried logging out and deleting cookies to attempt to force a new OAuth request from the application to request access, but it still just allows me to sign in and automatically jumps to the homepage.

[bbgrupojoven]

👍 I my case, i had to authorize the organization in the settings of the Guithub Issue Mover application. Looks like is just a configuration.

[boelle]

i get the same problem when i try to move an issue with more than about 35 comments on it

[boelle]

@bbgrupojoven how did you do that setup?

spec the Authorization callback URL... what should that be set to?

[boelle]

i can at least confirm that if there are more than 35 comments i cant move an issue :-(

[bbgrupojoven]

@boelle Enter to github settings

[boelle]

that far i came....

how did you setup the app itsself?

[bbgrupojoven]

I used the web page
https://github-issue-mover.appspot.com/

[boelle]

same here... coudl you show a pic of how you set up the app?

[boelle]

spec the last one......

[bbgrupojoven]

I did not configure any app.

2015-08-04 21:43 GMT+03:00 Bo Herrmannsen [email protected]:

same here... coudl you show a pic of how you set up the app?

—
Reply to this email directly or view it on GitHub
#11 (comment)
.

[wh81752]

Run into same problem as original issue reporter. Then I noticed, that I hadn't issue tracking enabled on my destination repository.

[ahundt]

I did have issue tracking enabled on mine

[roynasser]

Any light on this issue?

I'm having the same error... Tried numerous issues, with comments/without comments, and multiple desintation repos...

Source and Dest repo are in the same private user... I can see the info from the issue so I guess its authroized correctly... any other way of finding out the error that may be generated?

[gordonwoodhull]

I am a member of multiple organizations, so I had to further click on the Issue Mover application in the screenshot @bbgrupojoven showed, then authorize access to the particular organization I was moving from/to.

Which might be some change to the GitHub authorization scheme, because I know I successfully used this app before with two projects under the same organization. Anyway, works again now, yay.

[nmccready]

The issue move app is there for me in settings as well as the correct organization. However this issue happens on some issues not all. So I would say this is a bug somewhere.