* clean views.
* allow to create a stock.request with no analytic account.
* remove copy attribute in non-stored field.
* remove non-existing field from compute method.
Source is https://stackoverflow.com/a/49452683/1504003
with small adaptations (reset delay and retries when we get back a
connection)
Instead of creating the connection in the "main" method, loop and reopen
a new event loop on failures, let the Protocol class handle connections
and retries on failures.
Reduce keepalive interval and store values in attributes. As many
timeouts in systems are 60 seconds, a keepalive of 50 seconds is less
likely to be stopped.
Improve logs: the docstring of connection_lost is:
The argument is either an exception object or None. The latter means a
regular EOF is received, or the connection was aborted or closed by this
side of the connection.
When it receives no exception, it should not raise an error log.
The proxy would not exit properly in case of a lost connection with the JMIF server.
The change allows the proxy to exit, giving a chance to an external monitoring system
to restart the service.
A vertical lift retrieves a tray and places it in front of the
user, and depending on the quantity the user takes from it,
it adapts the pending quantity in the tray. However, because of
errors, it could be that the system thinks the tray is empty
while it is not. With this module, when the system thinks the
tray is empty, while in the step for the release of the tray
the operator is asked explicitly to check if the tray is
actually empty. Depending on his/her answer (yes/no) an inventory
adjustment is created stating the situation.
To activate this optional feature, a new configuration setting
has been added to Inventory > Configuration > Settings, named
'Check Empty Tray'. It is deactivated by default.
Developing decisions:
- The screens shown to the operator are actually wizards, but
since in the original module (`stock_vertical_lift`) they
were considered (on the source tree) as views, this has been
continued here.
- It has been decided, to not change the current workflow of
the operators, to embed the new check inside the step for
the 'release'. So, a new screen is shown to ask for the
visual inspection of whether the tray is empty. In
order to test this easily, the method `button_release` of
the module `stock_vertical_lift` has been slightly modified
so that it always returns. This way we can check easily
in the unit-tests for the outcome of the intermediate
screen (i.e. wizard) ─ similarly to how it is done when
validating a picking that can result in a backorder.
