I just tried it without any problem: http://issues.joomla.org/tracker/jtracker/416#event-32047

Not sure what is going wrong here :(

May be some kind of temp error or something. Let's wait and see will it happen again or not.

Just tried again. I see debug is on right now so the full stack error I get is

Is it permissions?

This comment was created with the J!Tracker Application at http://issues.joomla.org/.

Hmm... GitHub API says that it something wrong with the fields.

Sending invalid fields will result in a 422 Unprocessable Entity response.

Strange... I've added my test user bzz0 to editors group of JTracker project (it is the same as you are in) and tried to change the status of issue 416. No errors

I am just a user not a developer ;) I am just reporting what I see

On 31 August 2014 10:31, Dmitry Rekun notifications@github.com wrote:

Hmm... GitHub API says https://developer.github.com/v3/#client-errors
that it something wrong with the fields.

Sending invalid fields will result in a 422 Unprocessable Entity response.

Strange... I've added my test user bzz0 to editors group of JTracker
project (it is the same as you are in) and tried to change the status of
issue 416. No errors [image: ]

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

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Maybe its a permissions on github not on Jtracker?

On 31 August 2014 10:32, Brian Teeman brian@teeman.net wrote:

I am just a user not a developer ;) I am just reporting what I see

On 31 August 2014 10:31, Dmitry Rekun notifications@github.com wrote:

Hmm... GitHub API says https://developer.github.com/v3/#client-errors
that it something wrong with the fields.

Sending invalid fields will result in a 422 Unprocessable Entity response.

Strange... I've added my test user bzz0 to editors group of JTracker
project (it is the same as you are in) and tried to change the status of
issue 416. No errors [image: ]

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

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

@mbabker please note here when you will deploy then we will ask Brian to repeat.

Deployed

Just tried to reopen a closed issue and got this beautiful error

array(7) { ["exception"]=> string(21) "422 Validation Failed" ["user"]=>
string(6) "joomla" ["project"]=> string(7) "jissues" ["issueNo"]=>
string(3) "467" ["state"]=> string(4) "open" ["old_state"]=> string(6)
"closed" ["data"]=> array(10) { ["status"]=> string(1) "1" ["priority"]=>
string(1) "3" ["rel_type"]=> string(0) "" ["rel_number"]=> string(0) ""
["build"]=> string(1) "." ["easy"]=> string(1) "0" ["title"]=> string(12)
"Issue Status" ["description_raw"]=> string(367) "It appears we have two
different status selections. One is used in advanced search and one is used
on an issue. Can we just have one please
"
["id"]=> string(4) "4680" ["issue_number"]=> string(3) "467" } }
Unrecoverable GitHub error - sry ;(

On 2 September 2014 12:58, Michael Babker notifications@github.com wrote:

Deployed

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

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

@brianteeman here it works ok for me (i'm also "only" a JBS member): http://issues.joomla.org/tracker/joomla-cms/4204

Just tried to reopen a closed issue and got this beautiful error

Do you test it by changeing the status dropdown (closed --> open --> save --> closed --> save?) or have you a other way?

I cn confirm tht it works on on the CMS tracker - it appears to be just on this J!tracker (permissions??)

This comment was created with the J!Tracker Application at http://issues.joomla.org/.

Shouldn't be an issue with GitHub; the projects both have the issue bot
configured to it and the bot has access on the repo. Weird.

On Tue, Sep 2, 2014 at 12:30 PM, Brian Teeman notifications@github.com
wrote:

I cn confirm tht it works on on the CMS tracker - it appears to be just on
this J!tracker (permissions??)

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at
http://issues.joomla.org/http://issues.joomla.org/
http://issues.joomla.org/.

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

Was just an idea

On 2 September 2014 17:33, Michael Babker notifications@github.com wrote:

Shouldn't be an issue with GitHub; the projects both have the issue bot
configured to it and the bot has access on the repo. Weird.

On Tue, Sep 2, 2014 at 12:30 PM, Brian Teeman notifications@github.com
wrote:

I cn confirm tht it works on on the CMS tracker - it appears to be just
on
this J!tracker (permissions??)

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at
http://issues.joomla.org/http://issues.joomla.org/
http://issues.joomla.org/.

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

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

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Not a bad one, I did double check everything but don't see an apparent issue with the GitHub connection.

Should we add errors here to get them from GitHub? Like this may be:

$message = isset($error->message) ? $error->message . ' ' . $error->errors : 'Invalid response received from GitHub.';

@brianteeman is it still present?

Its fine now. I've changed lots of status since this and it hasnt happened again