Otherwise, the object could be modified (_p_changed=1) and reindexed for nothing.

See merge request nexedi/erp5!1462

See merge request nexedi/erp5!1483

query SlapOs Master again and again if it created accordingly the Computer
Partitions as anyway scalability tests will start only when instance's state is
reported to SlapOs Master as ready. Thus in this case this check (and requests
to SlapOs Master) is not providing any valuable information at all.

See merge request nexedi/erp5!1482

Increase instance creation time from 10 to 15 minutes as instance creation time includes its frontend creation which can take sometime a longer than usual time.

See merge request nexedi/erp5!1481

In practice, SFTP-based client processes often use a prefix based
filter when retrieving files on the server.

ie: there is one SFTP server between 2 systems, used for different
exchanges. The SFTP client will do something like (found in the wild):
process1(file_list=sftp.list(path, prefix='PROCESS_1'))
process2(file_list=sftp.list(path, prefix='PROCESS_2'))

Our implementation of temporary_file_on_write only sets a suffix,
which doesn't work for the previous SFTP client. So let's add also a
prefix when writing temporary files.

See merge request nexedi/erp5!1480

See merge request !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.

   Whenever used via activity nodes, it is not possible to discover IP of the server via portal absolute url.

See merge request nexedi/erp5!1478

   Only Person could include getFirstName and getLastName, so implement a fail-safe in case Login is inside a Computer or any other document.


(cherry picked from commit f7694fbc2ad2a22d582e48924732293ce1e96636)

  Ignore list is useful when you have old business templates in production (used to include data for example) and test business templates on test environment (ie;: erp5_test_ui_core).

  This allow us control the 'dump to assert' changes easily.

OSOE website is not necessarily part of standard configurator so only adjust if it is indeed installed.

See merge request nexedi/erp5!1476

(cherry picked from commit 1ad44735754d1701ffb12fecbb641602bfd01c8a)

Suite

Module erp5.component.document.erp5_version.ERP5ProjectUnitTestDistributor, line 326, in getTestSuiteSortKey
  wanted_test_core_quantity = PRIORITY_MAPPING[test_suite.getIntIndex()][1]
AttributeError: getIntIndex

Avoids the infamous 1024 file descriptor limit. No functional change
expected, as it seems unlikely this bug ever triggered on waitress-managed
file descriptors.

When using report sections with title, this is supposed to create outline
in PDF, but this seem to became broken somewhere in the last 10 years.

This repair by using text:h instead of text:p and by setting
text:outline-level

To activate it, we have a preference to allow users display or not ERP5 tools

This report proably needs to be updated more, but at least use proper
getAggregatedAmountList so it no longer crash

It was not enabled in ERP5JS had minor issues

See merge request !1473

match date field id in listbox's column

When jumping from a product to multiple transformations, there was no status
message and also ignore_hide_rows was not passed, which made this jump non
functional when the corresponding preference was enabled.

Same as 896e5cc8 (Allow to jump from Product to its related Transformation
using it as Material as well., 2011-12-13), but for Component.

`object_report` and `object_exchange` action categories are only enabled
in erp5_xhtml_style. Use the `jio` equivalent categories so that the
generated report is also enabled in ERP5JS.

OfficeJS use another mechanism for actions registration, so duplicate
actions defined on the portal type is not necessarly a problem, as long as
all actions are not registered in the same app.