See merge request nexedi/slapos.core!525

See merge request !523

  Since priority is 1 the activies can be called out of order. So calculateEtags can be called before all objects be indexed. This can lead to a intermediate (or old) value, requiring am extra call to the _activateFillComputeNodeInformationCache.

  This is somehow acceptable since the code should expect an ordering of activities execution anyway.

   This prevents to be delayed due excessive activities created by simulation

See merge request nexedi/slapos.core!520

   Dont fail if the Software Release couldnt be found, just stop (display error explanation) and allow the user to return where he came from.

  The string comes translated.

   This wasnt a proper update, and it was accidently commited by mistake on the MR.

See merge request nexedi/slapos.core!522

   The proper way is always wait for notification message after click proceed, since the spinning icon can flick between before the post and reload the page (probably because notifySubmitted).

   This tiny flickering can cause confuse the wait_for_content macro since it is called too soon.

   Mostly to translate Open allocation state (causing test to fail)

See merge request nexedi/slapos.core!518

   The selenium dont assert well with \n and code, so play safe and just assert line by line.

   This ensure data is saved before render a new form.

  This strips the form rendering from the parameter editor, and placing it as a stand alone editor (separated gadget).

   This allow us following the same API use other gadgets as parameter editors.

The path of the python executable used by an instance was parsed from
the shebang of its software release's bin/buildout. But when the path
is too long, the shebang is just /bin/sh and the script starts with
`exec <executable>`.

This fixes bug https://project.nexedi.net/#/bug_module/20210603-1C66F4F

See merge request !521

See fba76904

See merge request !519

See merge request !517

   Ignore to check if price matches if the invoice was created manually, and not linked to a business process.

See merge request !516

Improve hateoas support to show shared instances.

It turns out that ERP5 returns
```
'form_id': {
  'type': 'StringField',
  'key': 'form_id',
  'default': 'InstanceTree_viewAsHateoas',
},
```
for the `form_id` in hateoas, so adapt the proxy to do the same.

Currently hateoas support in proxy only lists non-shared instances,
so this always says that the instances are not shared.