- 21 Feb, 2019 3 commits
-
-
Alain Takoudjou authored
-
Alain Takoudjou authored
-
Alain Takoudjou authored
-
- 20 Feb, 2019 1 commit
-
-
Alain Takoudjou authored
-
- 18 Feb, 2019 1 commit
-
-
Alain Takoudjou authored
Use json.dumps/.loads to generate promise plugin code. This is safe as it will correctly escape sring and prevent code injection from untrustable parameters. Add 'import' parameter to simplify parameters used to generate the script instead of passing full import code. When import parameter is set, promise will be loaded from that import path and parameter `content` is ignored. /reviewed-on nexedi/slapos!515
-
- 15 Feb, 2019 3 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Julien Muchembled authored
-
- 14 Feb, 2019 2 commits
-
-
Guillaume Hervier authored
Close the NBD socket when testing it so it won't mess up qemu. /reviewed-on nexedi/slapos!516
-
Łukasz Nowak authored
-
- 12 Feb, 2019 1 commit
-
-
Łukasz Nowak authored
-
- 10 Feb, 2019 2 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
- 08 Feb, 2019 4 commits
-
-
Guillaume Hervier authored
- Add `buildout.hash.cfg` file so this way we can use the useful `update-hash` script - Refactor a bit the `software.cfg` file sections as it was repeating itself /reviewed-on nexedi/slapos!512
-
Łukasz Nowak authored
Extend the backend with Timeout configuration via headers and use it to prove, that request taking more than try_duration is correctly served. Also prove that try_duration and try_interval are correct passed to the slave configuration.
-
Łukasz Nowak authored
try_duration and try_interval are Caddy proxy's switches which allow to deal with non working backend (https://caddyserver.com/docs/proxy) The non working backend is the one, to which connection is lost or was not possible to make, without sending any data. The default try_duration=5s and try_interval=250ms are chosen, so that in normal network conditions (with all possible problems in the network, like lost packets) the browser will have to wait up to 5 seconds to be informed that backend is inaccessible or for the request to start being processed, but only a bit more than 250ms if Caddy would have to reestablish connection to faulty backend. In order to check it out it is advisable to setup a system, with real backend, like apache one, and configure iptables to randomly reject packets to it: iptables -A INPUT -m statistic --mode random -p tcp --dport <backend_port> \ --probability 0.05 -j REJECT --reject-with tcp-reset Using ab or any other tool will results with lot of 502 EOF in the Caddy error log and also reported by ab. With this configuration there are no more errors visible to the client, which come from the problems on the network between Caddy and the backend.
-
Łukasz Nowak authored
Assert itself "check_output" of given command, so provide simple subprocess_output with all possible information from the called command.
-
- 07 Feb, 2019 2 commits
-
-
Łukasz Nowak authored
Since slapos.core 1.4.16+ slapos proxy is not able to consume or publish non-strings, which makes tests not working.
-
Łukasz Nowak 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 3 commits
-
-
Alain Takoudjou authored
-
Alain Takoudjou authored
If qemu use physical disk device instead of created qemu image disk, we skip this promise. /reviewed-on nexedi/slapos!507
-
Alain Takoudjou authored
-
- 23 Jan, 2019 1 commit
-
-
Alain Takoudjou authored
-
- 22 Jan, 2019 6 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
-