Hi Lance
I was just running into the same issue as part of upgrading our
production server from release 2012_10_05 to 2013_02_08 (unfortunately,
I didn't catch it last week, when I did our test server, as the job
limit was not set there).
I added a little comment to your trello ticket, but
Hi Hans,
Thanks for bumping this thread. The issue has been fixed in development and
will be included in the next release.
--nate
On Mar 4, 2013, at 5:48 AM, Hans-Rudolf Hotz wrote:
Hi Lance
I was just running into the same issue as part of upgrading our production
server from release
Thanks Nate, it's much appreciated. I'm glad I was able to help out a
bit, just sorry I wasn't able to provide a complete fix (though maybe
that's for the best if there is a rewrite underway).
Lance
Nate Coraor wrote:
Hi Lance,
I'm rewriting much of this code, I should have all of it
Hi Lance,
I'm rewriting much of this code, I should have all of it committed (including
this fix) some time this week. Thanks for figuring out exactly what's going on
here.
--nate
On Jan 18, 2013, at 5:28 PM, Lance Parsons wrote:
Just an update on this issue. Upon further investigation, it
Just an update on this issue. Upon further investigation, it looks like
the dynamic job runner code in commit 6f3b4e8 broke this. I haven't been
able to parse through everything going on yet to propose a fix, but I've
discovered two things:
1) Moving the self.__clear_user_job_count() call
