- 07 Feb, 2019 13 commits
-
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Julien Muchembled authored
-
Julien Muchembled authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
Bryton Lacquement authored
-
- 06 Feb, 2019 1 commit
-
-
Alain Takoudjou authored
-
- 05 Feb, 2019 6 commits
-
-
Alain Takoudjou authored
-
Łukasz Nowak authored
Thanks to this 'None' is used in BuildoutSerializer
-
Kirill Smelkov authored
ZODB/go started to use it in tests: kirr/neo@532d014f
-
Kirill Smelkov authored
It started to be used in fs1/go.
-
Kirill Smelkov authored
https://github.com/kisielk/og-rek/compare/dd41cde712...8b25c4cefd - support for persistent references, - fixes for decoder and encoder, - allow to specify protocol on encoding, - support for protocols 3 and 4 including added support for Python bytes, - package-level documentation.
-
Julien Muchembled authored
-
- 30 Jan, 2019 1 commit
-
-
Jérome Perrin authored
-
- 29 Jan, 2019 3 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
update pep445 patch using https://raw.githubusercontent.com/vstinner/pytracemalloc/pytracemalloc-1.4/patches/2.7.15/pep445.patch
-
Thomas Gambier authored
-
- 24 Jan, 2019 1 commit
-
-
Alain Takoudjou authored
If qemu use physical disk device instead of created qemu image disk, we skip this promise. /reviewed-on nexedi/slapos!507
-
- 23 Jan, 2019 1 commit
-
-
Alain Takoudjou authored
-
- 22 Jan, 2019 9 commits
-
-
Kirill Smelkov authored
While helping @romain to review my current work we tried to build helloworld and found that it is completely broken. It was first minimally fixed to pin eggs and the like. Then I've added Go1.11 to our stack, so that recent-enough compiler/stdlib could be used. A note goes here that currently our lab uses go1.9 which is outdated and not supported by upstream, and other bits are still using go1.10.3 while go1.10.7 was already released some time ago with bug and security fixes. I did not touched neither go1.10 / nor go1.9, but imho it makes sense for infrastructure people to look into appropriate upgrades. Finally component/helloweb/ is switched to use gowork infrastructure (see 1b540151 for gowork introduction). Today gowork is used to build eveything go-related, so building go bits manually via cmmi as example is a bit misleading. Gowork is also required in case we'll need to use any third-party or our package a helloweb-go. /cc @luke, @alain.takoudjou /reviewed-by @jerome, @tomo /reviewed-on nexedi/slapos!505
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Kirill Smelkov authored
- it is gowork that is now used by Go-related bits in SlapOS, so using gowork is preferred as example. Besides we need gowork to be able to use any third-party Go package. - other languages can use helloweb repository from under gowork/ tree as well. The hash of helloweb.git is changed, becuase its layout had to be too adjusted to match gowork mode: nexedi/helloweb@a072af78...8bfedac6
-
Kirill Smelkov authored
To pick up Python3 support. nexedi/helloweb@39fd89a3...a072af78
-
Kirill Smelkov authored
Don't drop support for Go1.9, as, even though Go1.9 is no longer supported, software/gitlab depends on it. Our Go1.10.X is also too outdated, but I'm not touching it here neither. /cc @alain.takoudjou, @luke
-
Kirill Smelkov authored
2019-01-21 17:56:18 slapos[13553] INFO While: 2019-01-21 17:56:18 slapos[13553] INFO Installing. 2019-01-21 17:56:18 slapos[13553] INFO Getting section instance-profile. 2019-01-21 17:56:18 slapos[13553] INFO Initializing section instance-profile. 2019-01-21 17:56:18 slapos[13553] INFO Installing recipe slapos.recipe.template. 2019-01-21 17:56:18 slapos[13553] INFO Getting distribution for 'slapos.recipe.template'. 2019-01-21 17:56:18 slapos[13553] INFO Error: Picked: slapos.recipe.template = 4.3 2019-01-21 17:56:19 slapos[13553] ERROR Failed to run buildout profile in directory '/srv/slapgrid/slappart7/srv/runner/software/19771f7b751ffc2a88162b15750c6069' 2019-01-21 18:01:21 slapos[26771] INFO While: 2019-01-21 18:01:21 slapos[26771] INFO Installing. 2019-01-21 18:01:21 slapos[26771] INFO Getting section helloweb-ruby. 2019-01-21 18:01:21 slapos[26771] INFO Initializing section helloweb-ruby. 2019-01-21 18:01:21 slapos[26771] INFO Getting option helloweb-ruby:input. 2019-01-21 18:01:21 slapos[26771] INFO Getting section helloweb-ruby-bundle. 2019-01-21 18:01:21 slapos[26771] INFO Initializing section helloweb-ruby-bundle. 2019-01-21 18:01:21 slapos[26771] INFO Getting option helloweb-ruby-bundle:make-targets. 2019-01-21 18:01:21 slapos[26771] INFO Getting section bundler. 2019-01-21 18:01:21 slapos[26771] INFO Initializing section bundler. 2019-01-21 18:01:21 slapos[26771] INFO Installing recipe rubygemsrecipe. 2019-01-21 18:01:21 slapos[26771] INFO Getting distribution for 'rubygemsrecipe'. 2019-01-21 18:01:21 slapos[26771] INFO Error: Picked: rubygemsrecipe = 0.2.2+slapos001 Ruby stuff was failing to download at all -> let's use the versions that are the same as currently used in software/gitlab. Based on patch by @romain. Helped by @jerome.
-
Jérome Perrin authored
openss1.1 caused problems with bundler: Unable to require openssl, install OpenSSL and rebuild ruby (preferred) or use non-HTTPS sources
-
Jérome Perrin authored
/reviewed-on nexedi/slapos!504
-
- 21 Jan, 2019 1 commit
-
-
Thomas Gambier authored
They are dependencies of slapos.toolbox and we already agreed to put slapos.toolbox version in a shared file. /cc @jerome @jm /reviewed-on nexedi/slapos!502
-
- 18 Jan, 2019 1 commit
-
-
Alain Takoudjou authored
-
- 17 Jan, 2019 1 commit
-
-
Łukasz Nowak authored
One of solutions for random 502 errors from caddy is to fully disable HTTP2 protocol ( https://github.com/mholt/caddy/issues/1080 ) We run Caddy with HTTP2 enabled by default, as we can enable/disable it per each slave, but in some environments it might be just better to fully avoid HTTP2 codepaths in Caddy. /reviewed-on nexedi/slapos!495
-
- 16 Jan, 2019 2 commits
-
-
Łukasz Nowak authored
The IP used by frontend can be different than the real endpoint, and unknown for the frontend itself, so make it catch-all to allow access. /reviewed-on nexedi/slapos!497
-
Łukasz Nowak authored
Because of misleading tests (Accept-Encoding with gzip was always set by requests, fixed in "caddy-frontend/test: Workaround requests issue with Accept-Encoding") the original commit "Fix/caddy frontend prefer gzip type zope" did not really fixed the issue for type:zope backend.
-