[Krang-devel] strange problem introduced by my work on the undelete code

[Christopher H. <ch...@ch...>]

I had a story 109 and I deleted it using the API, but now the daemon is broke:

[04/19/05 15:34:18] [FINI_Sites] [info] 
Krang::Schedule::Daemon->scheduler_pass('FINI_Sites'): 3 jobs found.  Working..
[04/19/05 15:34:18] [FINI_Sites] [critical] 
Krang::Schedule::Daemon->_child_work('FINI_Sites'): Child PID=26406 encountered 
fatal error with Schedule ID=2016 : Krang::Schedule->_send(): Attempt to send 
alert failed: No valid Krang::Story object found with id 109 at 
/usr/local/krang/lib/Krang/Alert.pm line 431
         Krang::Alert::send('Krang::Alert','alert_id',1,'user_id',2,'story_id',109) 
called at /usr/local/krang/lib/Krang/Schedule.pm line 688
         eval {...} called at /usr/local/krang/lib/Krang/Schedule.pm line 687
         Krang::Schedule::_send('Krang::Schedule=HASH(0x212c7c0)') called at 
/usr/local/krang/lib/Krang/Schedule.pm line 549
         Krang::Schedule::execute('Krang::Schedule=HASH(0x212c7c0)') called at 
/usr/local/krang/lib/Krang/Schedule/Daemon.pm line 300
         eval {...} called at /usr/local/krang/lib/Krang/Schedule/Daemon.pm line 
300
         eval {...} called at /usr/local/krang/lib/Krang/Schedule/Daemon.pm line 
291
         Krang::Schedule::Daemon::_child_work('ARRAY(0x20e7220)') called at 
/usr/local/krang/lib/Krang/Schedule/Daemon.pm line 233
         Krang::Schedule::Daemon::scheduler_pass('Krang::Schedule=HASH(0x212c7c0)','Krang::Schedule=HASH(0x212b270)','Krang::Schedule=HASH(0x212c9e0)') 
called at /usr/local/krang/lib/Krang/Schedule/Daemon.pm line 165
         Krang::Schedule::Daemon::run('Krang::Schedule::Daemon') called at 
/usr/local/krang/bin/krang_scheduled line 51

The relevant items I believe are:

mysql> select * from alert where alert_id=1;
+----------+---------+---------+---------+-------------+
| alert_id | user_id | action  | desk_id | category_id |
+----------+---------+---------+---------+-------------+
|        1 |       3 | checkin |    NULL |        NULL |
+----------+---------+---------+---------+-------------+
1 row in set (0.02 sec)

mysql> select * from schedule where schedule_id=2016;
+-------------+--------+--------+------------------------------------+-------------+-----------+---------------------+----------+---------------------+-------------+------+--------+----------+
| schedule_id | repeat | action | context                            | 
object_type | object_id | initial_date        | last_run | next_run 
| day_of_week | hour | minute | priority |
+-------------+--------+--------+------------------------------------+-------------+-----------+---------------------+----------+---------------------+-------------+------+--------+----------+
|        2016 | never  | send   |                                 | alert 
|         1 | 2005-04-18 17:28:22 | NULL     | 2005-04-18 17:28:22 |   NULL | 
NULL |   NULL |        2 |
+-------------+--------+--------+------------------------------------+-------------+-----------+---------------------+----------+---------------------+-------------+------+--------+----------+
1 row in set (0.00 sec)

My guess is that I should just blow away schedule_id 2016 and all will be well, 
but before I do that I want to make sure that's reasonable.

-- 
</chris>

"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)