Roundup Tracker - Issues


Author rouilj
Recipients jlgijsbers, richard, rouilj, roysrapoport
Date 2016-07-04.19:56:50
Message-id <>
I took a look through the code and I wonder if this would work:

  have reactors optionally return an array of tuples:
     (exception, message)

in change:

   the call to:
     react(self.db, self, nodeid, oldvalues)
   to capture those tuples and store in:
   self.warning_exceptions[] where self is <hyperdb.Class "issue">
   that same object is created at cgi/
         before calling into rdbms_common (or back_anydbm I think)
   it looks like _editnodes can add info that gets sent back to the user.

I am not sure if adding a new prop into the issue is advisable. Seems
like it could be a hack.

It looks like cgi/ is set up to handle a MessageError and
report that to the user as an error. However as Richard said raising
MessageError will stop any further reactors from firing.

Too bad there isn't a queuing mechanism for exceptions where they
could be shoved in a queue (along with an id indicating that function
added the exception). Then they could be processed asynchronously by a
handler in a calling function at a higher level in the stack.

Kind of a soft exception that doesn't force the callee to return
immediately. Which may be what what richard was hinting at.

Also to test this just set the port number for smtp server in
config.ini to an unused port. Then send a message that triggers the
nosyreactor reactor.
Date User Action Args
2016-07-04 19:56:51rouiljsetmessageid: <>
2016-07-04 19:56:51rouiljsetrecipients: + rouilj, richard, jlgijsbers, roysrapoport
2016-07-04 19:56:51rouiljlinkissue859291 messages
2016-07-04 19:56:50rouiljcreate