- 07 Sep, 2021 1 commit
-
-
Xavier Thompson authored
This script reuses the promise launcher from slapos.core to launch the instance promises using the python executable installed by the SR.
-
- 06 Sep, 2021 2 commits
-
-
Xavier Thompson authored
This reverts commit a42d199a.
-
Xavier Thompson authored
-
- 03 Sep, 2021 3 commits
-
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-
- 02 Sep, 2021 4 commits
-
-
Léo-Paul Géneau authored
Add Software Release to provide scripts to run Time-Sensitive Networking motor demo.
-
Léo-Paul Géneau authored
-
Léo-Paul Géneau authored
-
Léo-Paul Géneau authored
-
- 01 Sep, 2021 1 commit
-
-
Łukasz Nowak authored
The python snippet has to print calculated value. This fixes commit 7d7a59d6 stack/cacuase: Make rerequest updatable
-
- 26 Aug, 2021 1 commit
-
-
Lu Xu authored
See merge request nexedi/slapos!994
-
- 24 Aug, 2021 4 commits
- 23 Aug, 2021 4 commits
-
-
Łukasz Nowak authored
See merge request !1013
-
Léo-Paul Géneau authored
- rubygemsrecipe deployment mode now depends on `allow-picked-versions` by default
-
Boxiang Sun authored
sotware/caddy-frontend: Use instance-caddy-replicate.cfg to replace buildout-switch-softwaretype.cfg Because when using the switch-software, the buildout-switch-sofwtwaretype.cfg will not be generated, see https://lab.nexedi.com/nexedi/slapos/blob/master/slapos/recipe/softwaretype.py#L264-267 So use instance-caddy-replicate.cfg instead, which has same effect.
-
Boxiang Sun authored
Changes explanation: slave_reference.lower(): The configparser which the current buildout using is case sensitive, which cause some options cannot be found. slap_software_type: The recipe softwaretype need this option, but switch-softwaretype doesn't. caddyprofiledeps: It provides the deps of caddy. Switch to switch-softwaretype leads to the error like "ImportError: No module named furl". Force caddyprofiledeps installed first can solve this issue.
-
- 20 Aug, 2021 10 commits
-
-
Julien Muchembled authored
-
Jérome Perrin authored
See theia's [changelog](https://github.com/eclipse-theia/theia/blob/v1.16.0/CHANGELOG.md#v1160---7292021), we update from 1.13.0 to 1.16.0. Changes specific to slapos port: * We set `warnOnPotentiallyInsecureHostPattern` because the new warning is very intrusive ... but it might actually be very insecure. For now we don't have solution. We are tracking this in https://erp5js.nexedi.net/#/bug_module/20210819-20614EE * New libsecret component that is now required by theia * Switch to using vscode git instead of theia git, to use timeline ( see https://github.com/eclipse-theia/theia/pull/7997 ) * globally version up slapos.core to https://pypi.org/project/slapos.core/1.6.18/ See merge request !1039
-
Jérome Perrin authored
-
Jérome Perrin authored
To have the timeline view
-
Jérome Perrin authored
This is basically the same problem as in 1b291415 (component/ghostscript: Workaround for slaprunner paths with double slashs, 2021-06-02)
-
Jérome Perrin authored
The issue is now fixed in 1.16.0
-
Jérome Perrin authored
Eventhough our current pattern is not the most secure, we have no other choice for now that to use such insecure patterns. In https://erp5js.nexedi.net/#/bug_module/20210819-20614EE we track possible improvements to this situation.
-
Jérome Perrin authored
This new version has a dependency to libsecret Also adjust dependencies to the ones from https://github.com/eclipse-theia/theia/blob/v1.16.0/examples/browser/package.json except api-samples which is not useful.
-
Jérome Perrin authored
-
Jérome Perrin authored
See merge request !1027
-
- 19 Aug, 2021 10 commits
-
-
Xavier Thompson authored
See merge request !931
-
Xavier Thompson authored
The resiliency pull-backup-server status feed file `pbs-status-rss` is generated by a cron running every 5 minutes. But there is a promise that requires it to check the notifier status, meaning instanciation fails until this file is available. To allow the promise to succeed immediately, we generate the feed a first time directly from buildout.
-
Xavier Thompson authored
The resiliency notifier status feed file `notifier-status-rss` is generated by a cron running every 5 minutes. But there is a promise that requires it to check the notifier status, meaning instanciation fails until this file is available. To allow the promise to succeed immediately, we generate the feed a first time directly from buildout.
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-
Xavier Thompson authored
-