- 10 Sep, 2021 3 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
Go1.17 is incremental improvement over Go1.16 with better and faster compiler, runtime, module-mode improvements and faster generated code: https://blog.golang.org/go1.17 https://golang.org/doc/go1.17 Drop support for Go1.15, as that release reached EOL and nothing currently uses it in SlapOS. Don't drop support for Go1.12 yet, as that long-ago-EOL and no longer supported Go release is still being used by software/gitlab. Remain default at Go1.16 yet. Switch helloworld to Go1.17 and test this patch on that software-release.
-
Kirill Smelkov authored
Going Go1.16.4 -> Go1.16.8 brings in fixes to compiler, runtime and stdlib including security fixes to net, crypto/tls, archive/zip, math/big, and net/http/httputil packages: https://golang.org/doc/devel/release.html#go1.16.minor Tested on helloworld SR.
-
- 08 Sep, 2021 2 commits
-
-
Ivan Tyagov authored
-
Łukasz Nowak authored
2021/09/07 : 2.0.25 - BUG/MEDIUM: sock: really fix detection of early connection failures in for 2.3- - REGTESTS: abortonclose: after retries, 503 is expected, not close - BUG/MEDIUM: base64: check output boundaries within base64{dec,urldec} - MINOR: compiler: implement an ONLY_ONCE() macro - BUG/MINOR: lua: use strlcpy2() not strncpy() to copy sample keywords - BUG/MINOR: ebtree: remove dependency on incorrect macro for bits per long - BUG/MINOR threads: Use get_(local|gm)time instead of (local|gm)time - BUG/MINOR: tools: Fix loop condition in dump_text() - CLEANUP: Add missing include guard to signal.h - DOC: configuration: remove wrong tcp-request examples in tcp-response - BUG/MINOR: config: reject configs using HTTP with bufsize >= 256 MB - CLEANUP: htx: remove comments about "must be < 256 MB" - BUG/MAJOR: htx: fix missing header name length check in htx_add_header/trailer - Revert "BUG/MINOR: stream-int: Don't block reads in si_update_rx() if chn may receive" - MINOR: action: Use a generic function to check validity of an action rule list - REGTESTS: mark http_abortonclose as broken
-
- 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 nexedi/slapos!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 nexedi/slapos!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 nexedi/slapos!1027
-
- 19 Aug, 2021 6 commits
-
-
Xavier Thompson authored
See merge request nexedi/slapos!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
-