divmod-dev team mailing list archive

[Jean-Paul Calderone <exarkun@xxxxxxxxxxxxxxxxx>]

Public bug reported:

This was filed in the old Divmod issue tracker as ticket 2963.

When axiomatic starts up, it does nothing special with the batch
processing system.  If application code explicitly requests something
from the remote batch processor, the batch process will get started up.
However, if there are pending items in need of remote processing, these
will not cause the batch process to start (so the items are not
processed).  And the creation of new items for remote processing is also
not sufficient to start the process.

This is hard to fix for real, but an improvement is to at least start
the batch process when new items for remote processing are created.

** Affects: divmod-axiom
     Importance: Undecided
         Status: New

** Branch linked: lp:~divmod-dev/divmod.org/batch-process-start-
heuristic-2963

-- 
You received this bug notification because you are a member of Divmod-
dev, which is the registrant for Divmod Axiom.
https://bugs.launchpad.net/bugs/910927

Title:
  The batch process is not started up automatically

Status in Divmod Axiom:
  New

Bug description:
  This was filed in the old Divmod issue tracker as ticket 2963.

  When axiomatic starts up, it does nothing special with the batch
  processing system.  If application code explicitly requests something
  from the remote batch processor, the batch process will get started
  up.  However, if there are pending items in need of remote processing,
  these will not cause the batch process to start (so the items are not
  processed).  And the creation of new items for remote processing is
  also not sufficient to start the process.

  This is hard to fix for real, but an improvement is to at least start
  the batch process when new items for remote processing are created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/divmod-axiom/+bug/910927/+subscriptions