GitHub sync duplicate
avatar brianteeman
brianteeman
9 Sep 2014

Steps to reproduce the issue

A user created two issues #4247 and #4248
I am guessing that 4247 was created at jissues and 4248 at github
To ensure we only had one issue for one item. I edited 4248 at github to have the description from 4247.

Expected result

I expected that this change at github to 4248 would be reflected at jissues

Actual result

4248 has not been updated

Additional comments

As people can edit comments in both places it is essential that both trackers sync on edits

avatar brianteeman brianteeman - open - 9 Sep 2014
avatar b2z b2z - change - 9 Sep 2014
Labels Added: GitHub sync
avatar b2z b2z - change - 9 Sep 2014
The description was changed
Labels Added: bug
avatar b2z b2z - change - 9 Sep 2014
Labels Added: enhancement
Removed: bug
avatar elkuku
elkuku - comment - 9 Sep 2014

Is this a duplicate of #213 ?

I checked joomla/joomla-cms#4248 against http://issues.joomla.org/tracker/joomla-cms/4248 and it looks OK now?

avatar brianteeman
brianteeman - comment - 9 Sep 2014

It sounds like it could be

avatar elkuku
elkuku - comment - 9 Sep 2014

So the edits from GitHub are now present on issues.joomla.org?

Just in case: These modifications are done by a cron job that runs periodically (I believe every hour (@mbabker?)).
So I guess in case that syncing becomes more critical (maybe a PBF event) the frequency the cron job is run could be raised to avoid confusion (@mbabker?:wink:).

avatar brianteeman
brianteeman - comment - 9 Sep 2014

Ah that explains it. How often is the cron run?

On 9 September 2014 14:28, Nikolai Plath notifications@github.com wrote:

So the edits from GitHub are now present on issues.joomla.org?

Just in case: These modifications are done by a cron job that runs
periodically (I believe every hour (@mbabker https://github.com/mbabker
?)).
So I guess in case that syncing becomes more critical (maybe a PBF event)
the frequency the cron job is run could be raised to avoid confusion (
@mbabker https://github.com/mbabker?[image: :wink:]).


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

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

avatar mbabker
mbabker - comment - 9 Sep 2014

Hourly for each repo.

On Tue, Sep 9, 2014 at 10:12 AM, Brian Teeman notifications@github.com
wrote:

Ah that explains it. How often is the cron run?

On 9 September 2014 14:28, Nikolai Plath notifications@github.com
wrote:

So the edits from GitHub are now present on issues.joomla.org?

Just in case: These modifications are done by a cron job that runs
periodically (I believe every hour (@mbabker https://github.com/mbabker

?)).
So I guess in case that syncing becomes more critical (maybe a PBF
event)
the frequency the cron job is run could be raised to avoid confusion (
@mbabker https://github.com/mbabker?[image: :wink:]).


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

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


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

avatar brianteeman
brianteeman - comment - 9 Sep 2014

Can we increase that to every 30 minutes?

On 9 September 2014 15:38, Michael Babker notifications@github.com wrote:

Hourly for each repo.

On Tue, Sep 9, 2014 at 10:12 AM, Brian Teeman notifications@github.com
wrote:

Ah that explains it. How often is the cron run?

On 9 September 2014 14:28, Nikolai Plath notifications@github.com
wrote:

So the edits from GitHub are now present on issues.joomla.org?

Just in case: These modifications are done by a cron job that runs
periodically (I believe every hour (@mbabker <
https://github.com/mbabker>

?)).
So I guess in case that syncing becomes more critical (maybe a PBF
event)
the frequency the cron job is run could be raised to avoid confusion (
@mbabker https://github.com/mbabker?[image: :wink:]).


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

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


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


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

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

avatar mbabker
mbabker - comment - 9 Sep 2014

Done. The only concern now is rate limiting since we still only have 1 bot set up.

avatar brianteeman brianteeman - close - 12 Sep 2014
avatar brianteeman brianteeman - close - 12 Sep 2014
avatar elkuku elkuku - close - 12 Sep 2014
avatar elkuku elkuku - close - 12 Sep 2014
avatar brianteeman brianteeman - change - 12 Sep 2014
Status New Closed
avatar brianteeman brianteeman - change - 12 Sep 2014
Closed_Date 0000-00-00 00:00:00 2014-09-12 13:20:21
avatar elkuku elkuku - change - 12 Sep 2014
Labels Removed: enhancement
avatar elkuku elkuku - change - 12 Sep 2014
Labels Added: duplicate
avatar b2z
b2z - comment - 11 Oct 2014

Joomla! Logo JTracker Status Comment


issues.joomla.org/tracker/jtracker/483

Easy: No
Successfull Tests: 0
Unsuccessfull Tests: 0


Last updated on 11 Oct 2014 19:53:49 GMT

Add a Comment

Login with GitHub to post a comment