- 30 Jan, 2018 6 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
-
- 29 Jan, 2018 20 commits
-
-
Tomáš Peterka authored
/reviewed-on nexedi/erp5!559
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tomáš Peterka authored
- remove hack when tests were using each others data by `markChanged` script
-
Tomáš Peterka authored
-
Tomáš Peterka authored
-
Tristan Cavelier authored
in erp5_run_my_doc, erp5_web_blog and erp5_credential Same reason as in 2115abc3. /reviewed-on nexedi/erp5!554
-
Xiaowu Zhang authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
This avoids relying on implementation details by only relying on regular API. This test should now be more robust in face of implementation changes.
-
Vincent Pelletier authored
Also, add an XXX about manage_test annoying behaviour.
-
- 25 Jan, 2018 4 commits
-
-
Romain Courteaud authored
-
Xiaowu Zhang authored
-
Vincent Bechu authored
-
Vincent Pelletier authored
-
- 24 Jan, 2018 5 commits
-
-
Vincent Bechu authored
-
Vincent Bechu authored
-
Vincent Bechu authored
-
Boxiang Sun authored
Avoids the double-nonsense of looking the document up by path inside callee (!) using the catalog (!!). Also, follow naming conventions: variables containing documents should end in _value, not in _object. Vincent Pelletier: - commit message - remove unrelated change - squash similar similar-intent commits even though they apply to different BTs
-
Vincent Pelletier authored
These methods must not be called synchronously: - they can break catalog by not being careful enough about other reindexations which may happen in parallel. See the serialization_tag mechanism for more. - indexation gets executed in the security context of the user causing the call, which may lead to an indexation result different from what happens when indexation happens with an all-accesses user. These lines of code (some even commented-out) give a bad example. Replace them with safe equivalents.
-
- 22 Jan, 2018 2 commits
-
-
Xiaowu Zhang authored
…r in (multi)relation field /reviewed-on !556
-
Vincent Pelletier authored
Such tables are not visible in the ZMI (which is arguably a bug on its own, although the ZMI is deprecated), but even accessing the setting tab is broken as it runs these methods. This change at least allows accessing stuff to start fixing.
-
- 19 Jan, 2018 3 commits
-
-
Sven Franck authored
-
Vincent Pelletier authored
The order in which messages are returned by getMessageList is undefined, and manageInvoke refuses to execute messages which are blocked by their dependencies. Notify depends on Alarm_runUpgrader, so it must be explicitly ran second. Also, avoid listing activities twice.
-
Vincent Pelletier authored
Here, we expect exactly two activities, one of each type, and just do not rely on these being listed in any order (...in theory, as this is actually assumed by the next iteration on getMessageList, but this is a separate issues).
-