- 05 Mar, 2023 1 commit
-
-
Jérome Perrin authored
See merge request nexedi/slapos.core!478
-
- 02 Mar, 2023 1 commit
-
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!495
-
- 01 Mar, 2023 3 commits
-
-
Jérome Perrin authored
This is no longer guessed on Zope4
-
Jérome Perrin authored
this way we can just assert the full page content
-
Jérome Perrin authored
this does not depend on the details of the URL
-
- 28 Feb, 2023 2 commits
-
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!493
-
Rafael Monnerat authored
.. on consistency table
-
- 27 Feb, 2023 4 commits
-
-
Xavier Thompson authored
See merge request nexedi/slapos.core!489
-
Xavier Thompson authored
See merge request !490
-
Thomas Gambier authored
This was introduced in 081e745e and I don't see how it could have been useful.
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!494
-
- 24 Feb, 2023 2 commits
-
-
Rafael Monnerat authored
It was used on OrderBuilder_generateUnrelatedInvoiceList but the code dont relies on it anymore.
-
Rafael Monnerat authored
-
- 17 Feb, 2023 13 commits
-
-
Romain Courteaud authored
Only one line is used per document. Using REPLACE is better than DELETE / INSERT.
-
Romain Courteaud authored
No need for a multi column primary key, as only one line is used per object. This will speed up update of the table.
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!492
-
Jérome Perrin authored
This is no longer guessed on Zope4
-
Jérome Perrin authored
this way we can just assert the full page content
-
Jérome Perrin authored
this does not depend on the details of the URL
-
Jérome Perrin authored
This change is from zope4
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
An error slipped in 92da569e (slapos_jio: Drop Handlebars, 2022-06-08)
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
The forms were removed long ago, and those actions werent removed
-
- 15 Feb, 2023 2 commits
-
-
Xavier Thompson authored
When forwarding a request to an external master, e.g. frontend request, the master might first answer with status code 408 to indicate the requested resource is not ready. The slap library wraps the answer into a ComputerPartition object, even when the master sends 408: in that case the object only contains the parameters of the original request. Until now, when the external master answered 408, the proxy simply forwarded the ComputerPartition object returned by the slap library with code 200, instead of forwarding code 408. This played against the assumptions of the slap library in the client on the receiving end, resulting in a crash. This was the case even when using `requestoptional` recipe in buildout. Now the proxy detects when the object returned by the slap library is actually the result of a 408 answer, and aborts with code 408.
-
Xavier Thompson authored
-
- 13 Feb, 2023 1 commit
-
-
Rafael Monnerat authored
See merge request !488
-
- 10 Feb, 2023 3 commits
-
-
Rafael Monnerat authored
Most liketly a copy and paste mistake
-
Rafael Monnerat authored
Whenever you define a slave, the option_index inst the software-type but the property of the dict/object.
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!487
-
- 09 Feb, 2023 1 commit
-
-
Rafael Monnerat authored
This category is used whenever the user wants disallow allocation for the time been. It do not intend to re-open again after a procedure or do not intend to terminate the machine, just dont want anything be allocated on it.
-
- 07 Feb, 2023 7 commits
-
-
Rafael Monnerat authored
See merge request nexedi/slapos.core!486
-
Rafael Monnerat authored
category close and not closed, and do not auto cancel upgrades for computers for termination. This should be handled by setting never on upgrade scope.
-
Rafael Monnerat authored
Those actions were dropped from ancient site and forgotten to be removed.
-
Rafael Monnerat authored
Only Monitor Scope should be taken into account.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Whenever allocation scope changes, the capacity is close, and the proper alarm will re-open it later a moment after. This prevents when you change from close to open, to get a miss-updated window, and something is allocated before it capacity is calculated. Do not touch on monitor scope, except when it is None or allocation is "Close Forever", this allow the user to keep monitoring closed computers (Maintenance, termination...), since ONLY allocation is closed, and the computer is supposed to work normally with whatever is inside.
-
Rafael Monnerat authored
-