Only catch exceptions, we don't need a bare except here. In case of
exception, log the traceback instead of being silent.

Since https://github.com/zopefoundation/Zope/commit/2da2c2c28a8b21e78e8ef93aa17da926e3102c26
SERVER_PORT is assumed to be convertible to int.

The value of this port is not really supposed to be used because
TimerServer requests does not have a server (for example in CMFActivity
we recreate the initial request), so put a value of -1 to prevent
accidental use.

When running with ZServer, TimerServer will be started by ZConfig
machinery, because ZServer comes with some ZConfig data types for server
factory which start servers.

One Zope 2, ZServer was imported from zopeschema:

https://github.com/zopefoundation/Zope/blob/2.13.30/src/Zope2/Startup/zopeschema.xml#L10

and ZConfig used the TimerServerFactory to create a TimerService.

On Zope 4, ZServer is not imported anymore in the new wsgischema:

https://github.com/zopefoundation/Zope/blob/4.6.3/src/Zope2/Startup/wsgischema.xml

so the ZConfig data type can not be used to create the server.

Instead of relying on ZServer's ZConfig, we create the server directly
from the startup script, the logic to attach to waitress is already here
and startup and factory just called create, so the only difference is
that we no longer use zope.conf to configure TimerService, but configure
from the script.

SlapOS profile also needs to be modified in order to not include ZConfig
bits for timerserver and to pass the timerserver interval in the wrapper
to this script.

See merge request nexedi/erp5!1485

These are clone of Computer and Computer Partition, but used for virtual
computing devices, unrelated to physical hardware.

erp5_administration: Add Scripts for Alarm to update validation state according to consistency state

    If two open orders are validated on the same transaction, archivePrevious script will get the an already archived as catalog will be outdated.

   This allow the administrator define which Login portal types are searched.

Also extend tests to cover recently changes

   This is an alternetive way to login using Certificates. Probably this format
   will evolve into use caucase;  however this only introduce some most basic features.

   Use Certificate Login for store login definitions

  Please squash me in future.

  If the user wants actitivites, it should create multiples StandardBT5ConfiguratorItems,
  This should accellerate Tests based on ERP5Configurator.

  This should be recoded, but it should speed up bootstrap of a site,
  as get modified objects are not called.

It the user don't have fully permission on the object (already changed state), this set will fail to check if source should be defined.

  The upgrade ordering seems buggy and requires to force reinstall it

This allow during a subscription process, create a user and them create all
documents using that user w/o rely on proxy roles (keeping good ownership
across the documents).

Without this (on slapos master ui) the redirection places value unquoted causing parser to fail later on when resolve {n.me}

  The user can be present from diferent logins, password tool only works with ERP5LoginUserMager
  users.

Mixed commit:

  43b1ae1bc46b453e4553a9bc1077fe86e5db13bb
  2f05fe1b585d3ca736538b32269d36a410f5f7da

Returning true allows to add movements to existing one, and this group shall
always separate them.

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision

If 2 lines have the same effective date (catalog has a 1 second precision),
always return the validate and open first.

Commit: 02d06501ce38bc24d5d045968a53017d9b96b312

Changes applied from history:

http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1

Original commit from : Lukasz Nowak <luke@nexedi.com>
                       3e45ec35e38c008b0f8c2ceec73d7bb9dc62e2c0

Conflicts:
	bt5/erp5_crm/bt/revision

See merge request nexedi/erp5!1480

See merge request nexedi/erp5!1479

See merge request nexedi/erp5!1477

    This allow including more items to be ignored, preventing diffs from pure development.

  Those 2 exceptions are from SlapOS Master codebase, and for now we cannot remove it.

  Rather them complexify the ignore lists, we are hardcoding the values for minimase the ignore list
  to the least entries as possible.

  This is required for multiple sites support and allow us write unit tests and not create a 100 lines mock.