My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 15: Possible for status to get stuck in executing during debugging.
2 people starred this issue and may be notified of changes. Back to list
Status:  Started

Sign in to add a comment
Reported by, Jun 5, 2009
What steps will reproduce the problem?
1.  Ending program between status.executing=True and status.executing=False in 
CronScheduler.execute.  Can easily occur during debugging.

From then on the status is stuck in executing and no cron jobs will run.

Easy fix would be to set status.executing=False at the same time as all the old jobs are deleted 
during import of the module.

Jun 11, 2009
Project Member #1
Good call... I'll add that in on my next commit :)
Status: Accepted
Owner: Jim.mixtake
Jun 11, 2009
I have the same problem.
Jun 12, 2009
Project Member #3
I have this issue as well, I just didn't consider that people might use the same
database in development as they do on the live server, but it's definitely worth fixing!
Status: Started
Sign in to add a comment

Powered by Google Project Hosting