https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292008-09-25T19:04:55ZRedmineRedmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=49512008-09-25T19:04:55ZEric Davis
<ul></ul><p>+1 I ended up turning off my SCM's autofetch commits and have a cronjob as a workaround. Problem is, the cronjob only runs every hour so my Redmine is always behind.</p> Redmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=49532008-09-25T19:32:58ZNicolas Chuche
<ul></ul><p>Eric Davis wrote:</p>
<blockquote>
<p>+1 I ended up turning off my SCM's autofetch commits and have a cronjob as a workaround. Problem is, the cronjob only runs every hour so my Redmine is always behind.</p>
</blockquote>
<p>Using cron is the recommended way to do. I've worked on local cache for subversion and git (in branches/nbc for the moment) to speed things up but even than, creating a svnmirror of a repository can take a loooooong time.</p>
<p>We've talked about using something like backgroundrb instead of cron but it's not a priority for the moment. I would like to do other things before that.</p>
<p>I'm very bad in js so if someone can drop me a patch implementing the observer part Thomas speak about, I could try to implement the rails part.</p> Redmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=50022008-10-02T00:43:11ZEric Davis
<ul></ul><p>Nicolas Chuche wrote:</p>
<blockquote>
<p>I'm very bad in js so if someone can drop me a patch implementing the observer part Thomas speak about, I could try to implement the rails part.</p>
</blockquote>
<p>Don't think the observer would be that difficult. You can use <code>periodically_call_remote</code> from Rails with it pointed to an action that checks the status of the process. The action would return a busy if the process is still working or the response if it's complete (e.g. the updated svn browser)</p>
<blockquote>
<p>We've talked about using something like backgroundrb instead of cron but it's not a priority for the moment. I would like to do other things before that.</p>
</blockquote>
<p>I'd agree with you there. Ideally I would like to get some other improvements in Redmine before we optimize things.</p> Redmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=255692011-02-24T09:11:22ZEtienne Massip
<ul><li><strong>Category</strong> set to <i>SCM</i></li></ul> Redmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=460422013-02-25T10:08:33ZGabriel Mazetto
<ul></ul><p>This sounds like Delayedjobs or better Sidekiq could be optionally used here... This is a good time to start thinking about it, because Rails 4 will arrive with a Queue API, so more and more applications will start using async jobs.</p> Redmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=643172015-06-20T10:26:29ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-3 priority-lowest" href="/issues/2824">Defect #2824</a>: MySQL Deadlock Error when showing a big repository</i> added</li></ul> Redmine - Defect #1931: Timeout risks: need asynchronous operationshttps://www.redmine.org/issues/1931?journal_id=707822016-05-08T04:00:40ZGo MAEDA
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/70782/diff?detail_id=55002">diff</a>)</li></ul>