On Friday 01 of March 2013 13:49:55 Duncan Mac-Vicar P. wrote:
On 02/28/2013 10:13 PM, Tomas Lestach wrote:
The only part of code, that generates the repodata is the taskomatic
reporegen worker. I'd suggest to set the state to 'in progress' after a
generation starts, to set it to 'failed'
While it is easy to calculate the status of the repo-sync, -- as every
channel sync has _one_ taskomatic job which has a result --, the status
of the metadata generation is in _one_ Taskomatic job which creates
workers for every channel. However the status is lost one it runs. The
items in
- Original Message -
On 02/14/2013 05:59 PM, Tomas Lestach wrote:
Hi Duncan,
thanks for your patches.
I committed following:
eb7beb3277fb8db48376e44c058bde8ad5d1be45
1db45d611fbc307b4eac1fa35d25ed3b30dc6fac
668f52d928590b4bc7e2d3c955f2b6a59e5d3fb8
I didn't commit
On 02/14/2013 05:59 PM, Tomas Lestach wrote:
Hi Duncan,
thanks for your patches.
I committed following:
eb7beb3277fb8db48376e44c058bde8ad5d1be45
1db45d611fbc307b4eac1fa35d25ed3b30dc6fac
668f52d928590b4bc7e2d3c955f2b6a59e5d3fb8
I didn't commit following ones:
*TaskoRun Log tail: Handle
The following patches improve the status of a channel by taking into
account both download/mirror _and_ repodata generation.
The download/sync status was a bit tricky to get, as the taskomatic
table is made polymorphic by serializing java objects which in turn
contain the channel_id, so you
