- 19 Jul, 2016 3 commits
-
-
Kirill Smelkov authored
From upcoming https://golang.org/doc/devel/release.html#go1.6.minor go1.6.3 (released 2016/07/17) includes security fixes to the net/http/cgi package and net/http package when used in a CGI environment. This release also adds support for macOS Sierra. See the Go 1.6.3 milestone[1] on our issue tracker for details. [1] https://github.com/golang/go/issues?q=milestone%3AGo1.6.3 /reviewed-by TrustMe (tested with helloworld)
-
Kirill Smelkov authored
To pick up output \n and language/runtime version in output. nexedi/helloweb@0487fa7b...39fd89a3 /reviewed-by TrustMe
-
Jérome Perrin authored
@jerome says at 5f5d5102 (comment 17119): before f4e51f77, we had: `~/srv/runner/instance/slappart0/bin/gitlab-rake` containing: ```python ... if __name__ == '__main__': sys.exit(slapos.recipe.librecipe.execute.generic_exec((['/srv/slapgrid/slappart16/srv/runner/software/fffb3c99781923d3adb8bc53eb6c027a/bin/bundle', 'exec', 'sh', '-c', 'cd /srv/slapgrid/slappart16/srv/runner/instance/slappart0/gitlab-work && rake "$@"', 'rake'], None, {'BUNDLE_GEMFILE': '/srv/slapgrid/slappart16/srv/runner/software/fffb3c99781923d3adb8bc53eb6c027a/parts/gitlab/Gemfile', 'HOME': '/srv/slapgrid/slappart16/srv/runner/instance/slappart0', 'SIDEKIQ_MEMORY_KILLER_MAX_RSS': '1000000', 'RAILS_ENV': 'production'}))) ``` after, `~/srv/runner/instance/slappart0/bin/gitlab-rake` contains: ```shell #!/bin/bash COMMAND=/srv/slapgrid/slappart16/srv/runner/instance/slappart0/bin/gitlab-rake.py # If the wrapped command uses a shebang, execute the referenced # executable passing the script path as first argument. # This is to workaround the limitation of 127 characters in #! if [[ -f $COMMAND && x$(head -c2 "$COMMAND") = x"#!" ]]; then SHEBANG=$(head -1 "$COMMAND") INTERPRETER=( ${SHEBANG#\#!} ) COMMAND="${INTERPRETER[@]} $COMMAND" fi exec $COMMAND ``` which is a wrapper around `gitlab-rake.py` containing: ```python ... if __name__ == '__main__': sys.exit(slapos.recipe.librecipe.execute.generic_exec((['/srv/slapgrid/slappart16/srv/runner/software/fffb3c99781923d3adb8bc53eb6c027a/bin/bundle', 'exec', 'sh', '-c', 'cd /srv/slapgrid/slappart16/srv/runner/instance/slappart0/gitlab-work && rake "$@"', 'rake'], None, {'BUNDLE_GEMFILE': '/srv/slapgrid/slappart16/srv/runner/software/fffb3c99781923d3adb8bc53eb6c027a/parts/gitlab/Gemfile', 'HOME': '/srv/slapgrid/slappart16/srv/runner/instance/slappart0', 'SIDEKIQ_MEMORY_KILLER_MAX_RSS': '1000000', 'RAILS_ENV': 'production'}))) ``` `gitlab-rake.py` after is same as `gitlab-rake` before. This [slapos.cookbook:wrapper](https://lab.nexedi.com/nexedi/slapos/blob/cd9faac0/slapos/recipe/wrapper.py#L39) has an argument *parameters-extra* which if set to true, propagate command line arguments to the wrapped script. The default value for this parameter is false. Before f4e51f77, the generated wrapper was also propagating arguments even when *parameters-extra* was not set, but since this commit, this *parameters-extra* option is now handled as expected. This is the reason for this regression. In our case, when we see `/srv/slapgrid/slappart16/srv/runner/instance/slappart0/bin/gitlab-rake assets:clean`, it just calls `rake` without arguments. So a simple patch that fix the problem would be jerome/slapos@d3d05f02 . This way, the generated wrapper becomes: ```shell ... exec $COMMAND $@ ``` and arguments are correctly propagated. Feel free to cherry-pick that patch for now, but it may be nice to rethink this *parameters-extra* option, after this debugging session, I believe it should be true by default. /cc @seb for introducing the parameter in 80bb4305 and @vpelletier for touching this code in e7083872 /reviewed-by @kirr
-
- 15 Jul, 2016 2 commits
-
-
Tristan Cavelier authored
-
Kazuhiko Shiozaki authored
-
- 14 Jul, 2016 1 commit
-
-
Kirill Smelkov authored
/reviewed-by: TrustMe
-
- 13 Jul, 2016 12 commits
-
-
Rafael Monnerat authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
- logrotate: make stack with cfg.in containing sections for logrotating with dcron and gzip - neoppod: use this logrotate stack
-
Julien Muchembled authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
-
Tristan Cavelier authored
- apache: add generic configuration file for backend - erp5: make balancer use generic apache backend configuration file
-
Tristan Cavelier authored
-
- 11 Jul, 2016 1 commit
-
- 08 Jul, 2016 1 commit
-
-
Rafael Monnerat authored
-
- 06 Jul, 2016 4 commits
-
-
Kirill Smelkov authored
1.6.X is current stable series of Go. https://golang.org/doc/go1.6 https://golang.org/doc/devel/release.html#go1.6 So switch helloweb and default golang to it. /reviewed-by TrustMe (tested on helloworld)
-
Kirill Smelkov authored
From https://golang.org/doc/devel/release.html#go1.5.minor: go1.5.4 (released 2016/04/12) includes two security fixes. It contains the same fixes as Go 1.6.1 and was released at the same time. See the Go 1.6.1 milestone[1] on our issue tracker for details. [1] https://github.com/golang/go/issues?q=milestone%3AGo1.6.1 /reviewed-by TrustMe (tested with helloworld)
-
Vincent Pelletier authored
Avoids being spammed with WARNING ZODB.DB DB.open() has X open connections with a pool_size of 7 on zopes with more than 7 worker threads. Also, allows better hit-rate on volatile attributes in such case, as otherwise connections (and their cache) would be discarded when many threads would be made busy, decreasing performance.
-
Jérome Perrin authored
This works around https://github.com/buildout/buildout/issues/159
-
- 04 Jul, 2016 11 commits
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Julien Muchembled authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
This violates "instanciation happens offline" rule and project which initiated this need do not use it anymore.
-
Jérome Perrin authored
This patch change the log format from: ``` 2016-03-25 04:26:37,609 WARNING access 172.17.0.2 - Anonymous [25/Mar/2016:04:26:37 +0200] "GET / HTTP/1.0" 200 0 "" "" ------ 2016-03-25 04:26:37,613 WARNING access 172.17.0.2 - Anonymous [25/Mar/2016:04:26:37 +0200] "GET / HTTP/1.0" 200 1971 "" "" ------ 2016-03-25 04:26:37,619 WARNING access 172.17.0.2 - Anonymous [25/Mar/2016:04:26:37 +0200] "GET / HTTP/1.1" 200 1952 "" "" ------ 2016-03-25 04:26:40,619 WARNING access 172.17.0.2 - Anonymous [25/Mar/2016:04:26:40 +0200] "GET / HTTP/1.0" 200 1971 "" "" ------ 2016-03-25 04:26:43,622 WARNING access 172.17.0.2 - Anonymous [25/Mar/2016:04:26:43 +0200] "GET / HTTP/1.0" 200 1971 "" "" ``` to something more concise for the eye: ``` 2016-04-06 10:13:41,854 WARNING access 172.17.0.2 - Anonymous [06/Apr/2016:10:13:41 +0200] "GET / HTTP/1.0" 200 1971 "" "" 2016-04-06 10:13:44,861 WARNING access 172.17.0.2 - Anonymous [06/Apr/2016:10:13:44 +0200] "GET / HTTP/1.0" 200 1971 "" "" 2016-04-06 10:13:47,868 WARNING access 172.17.0.2 - Anonymous [06/Apr/2016:10:13:47 +0200] "GET / HTTP/1.0" 200 1971 "" "" 2016-04-06 10:13:50,875 WARNING access 172.17.0.2 - Anonymous [06/Apr/2016:10:13:50 +0200] "GET / HTTP/1.0" 200 1971 "" "" 2016-04-06 10:13:53,882 WARNING access 172.17.0.2 - Anonymous [06/Apr/2016:10:13:53 +0200] "GET / HTTP/1.0" 200 1971 "" "" 2016-04-06 10:13:56,890 WARNING access 172.17.0.2 - Anonymous [06/Apr/2016:10:13:56 +0200] "GET / HTTP/1.0" 200 1971 "" "" ``` by changing the log format from the default `------\n%(asctime)s %(levelname)s %(name)s %(message)s` ( defined [here](https://github.com/zopefoundation/ZConfig/blob/0d6a8a1/ZConfig/components/logger/handlers.xml#L38 )) to simply `%(asctime)s %(levelname)s %(name)s %(message)s` It is enabled for both event.log and Z2.log /cc @kazuhiko @vpelletier @tc /reviewed-on nexedi/slapos!67
-
- 30 Jun, 2016 1 commit
-
-
Tristan Cavelier authored
/reviewed-on nexedi/slapos!82
-
- 29 Jun, 2016 1 commit
-
-
Alain Takoudjou authored
-
- 28 Jun, 2016 2 commits
-
-
Alain Takoudjou authored
-
Alain Takoudjou authored
The problem is explaned here: https://bugs.chromium.org/p/chromium/issues/detail?id=260239 The use of header Vary: Origin dosen't fix the problem on chrome so I disabled the cache with Pragma "no-cache". This doesn't cause issue because most of monitor files are modified every minutes and sync happen at least every 5 minutes. So the better solution is to disable cached.
-
- 27 Jun, 2016 1 commit
-
-
Tristan Cavelier authored
fixing segmentation fault on css opacity rendering /reviewed-on !81
-