- 25 Feb, 2016 5 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
2.7.0 -> 2.7.2 is a bugfix release with several fixes: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.7.1.txt https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.7.2.txt
-
Kirill Smelkov authored
1.9.4 -> 1.9.12 adds HTTP/2 support and removes SPDY support + other bugfixes and improvements. We need HTTP/2 support for GitLab 8.5. HTTP/2 details: http://hg.nginx.org/nginx/rev/257b51c37c5a Full changelog: ---- 8< ---- http://nginx.org/en/CHANGES Changes with nginx 1.9.12 24 Feb 2016 *) Feature: Huffman encoding of response headers in HTTP/2. Thanks to Vlad Krasnov. *) Feature: the "worker_cpu_affinity" directive now supports more than 64 CPUs. *) Bugfix: compatibility with 3rd party C++ modules; the bug had appeared in 1.9.11. Thanks to Piotr Sikora. *) Bugfix: nginx could not be built statically with OpenSSL on Linux; the bug had appeared in 1.9.11. *) Bugfix: the "add_header ... always" directive with an empty value did not delete "Last-Modified" and "ETag" header lines from error responses. *) Workaround: "called a function you should not call" and "shutdown while in init" messages might appear in logs when using OpenSSL 1.0.2f. *) Bugfix: invalid headers might be logged incorrectly. *) Bugfix: socket leak when using HTTP/2. *) Bugfix: in the ngx_http_v2_module. Changes with nginx 1.9.11 09 Feb 2016 *) Feature: TCP support in resolver. *) Feature: dynamic modules. *) Bugfix: the $request_length variable did not include size of request headers when using HTTP/2. *) Bugfix: in the ngx_http_v2_module. Changes with nginx 1.9.10 26 Jan 2016 *) Security: invalid pointer dereference might occur during DNS server response processing if the "resolver" directive was used, allowing an attacker who is able to forge UDP packets from the DNS server to cause segmentation fault in a worker process (CVE-2016-0742). *) Security: use-after-free condition might occur during CNAME response processing if the "resolver" directive was used, allowing an attacker who is able to trigger name resolution to cause segmentation fault in a worker process, or might have potential other impact (CVE-2016-0746). *) Security: CNAME resolution was insufficiently limited if the "resolver" directive was used, allowing an attacker who is able to trigger arbitrary name resolution to cause excessive resource consumption in worker processes (CVE-2016-0747). *) Feature: the "auto" parameter of the "worker_cpu_affinity" directive. *) Bugfix: the "proxy_protocol" parameter of the "listen" directive did not work with IPv6 listen sockets. *) Bugfix: connections to upstream servers might be cached incorrectly when using the "keepalive" directive. *) Bugfix: proxying used the HTTP method of the original request after an "X-Accel-Redirect" redirection. Changes with nginx 1.9.9 09 Dec 2015 *) Bugfix: proxying to unix domain sockets did not work when using variables; the bug had appeared in 1.9.8. Changes with nginx 1.9.8 08 Dec 2015 *) Feature: pwritev() support. *) Feature: the "include" directive inside the "upstream" block. *) Feature: the ngx_http_slice_module. *) Bugfix: a segmentation fault might occur in a worker process when using LibreSSL; the bug had appeared in 1.9.6. *) Bugfix: nginx could not be built on OS X in some cases. Changes with nginx 1.9.7 17 Nov 2015 *) Feature: the "nohostname" parameter of logging to syslog. *) Feature: the "proxy_cache_convert_head" directive. *) Feature: the $realip_remote_addr variable in the ngx_http_realip_module. *) Bugfix: the "expires" directive might not work when using variables. *) Bugfix: a segmentation fault might occur in a worker process when using HTTP/2; the bug had appeared in 1.9.6. *) Bugfix: if nginx was built with the ngx_http_v2_module it was possible to use the HTTP/2 protocol even if the "http2" parameter of the "listen" directive was not specified. *) Bugfix: in the ngx_http_v2_module. Changes with nginx 1.9.6 27 Oct 2015 *) Bugfix: a segmentation fault might occur in a worker process when using HTTP/2. Thanks to Piotr Sikora and Denis Andzakovic. *) Bugfix: the $server_protocol variable was empty when using HTTP/2. *) Bugfix: backend SSL connections in the stream module might be timed out unexpectedly. *) Bugfix: a segmentation fault might occur in a worker process if different ssl_session_cache settings were used in different virtual servers. *) Bugfix: nginx/Windows could not be built with MinGW gcc; the bug had appeared in 1.9.4. Thanks to Kouhei Sutou. *) Bugfix: time was not updated when the timer_resolution directive was used on Windows. *) Miscellaneous minor fixes and improvements. Thanks to Markus Linnala, Kurtis Nusbaum and Piotr Sikora. Changes with nginx 1.9.5 22 Sep 2015 *) Feature: the ngx_http_v2_module (replaces ngx_http_spdy_module). Thanks to Dropbox and Automattic for sponsoring this work. *) Change: now the "output_buffers" directive uses two buffers by default. *) Change: now nginx limits subrequests recursion, not simultaneous subrequests. *) Change: now nginx checks the whole cache key when returning a response from cache. Thanks to Gena Makhomed and Sergey Brester. *) Bugfix: "header already sent" alerts might appear in logs when using cache; the bug had appeared in 1.7.5. *) Bugfix: "writev() failed (4: Interrupted system call)" errors might appear in logs when using CephFS and the "timer_resolution" directive on Linux. *) Bugfix: in invalid configurations handling. Thanks to Markus Linnala. *) Bugfix: a segmentation fault occurred in a worker process if the "sub_filter" directive was used at http level; the bug had appeared in 1.9.4. ---- 8< ----
-
Kirill Smelkov authored
Redis 2.8.23 -> 2.8.24 is a small bugfix release: --[ Redis 2.8.24 ] Release date: 18 Dec 2015 Upgrade urgency: MODERATE. We fixed a crash that happens very rarely, so updating does not hurt, but most users are unlikely to experience this condition because it requires some odd timing. * [FIX] lua_struct.c/getnum security issue fixed. (Luca Bruno discovered it, patched by Sun He and Chris Lamb) * [FIX] Fix a race condition in processCommand() because of interactions with freeMemoryIfNeeded(). Details in issue #2948 and especially in the commit message d999f5a. (Race found analytically by Oran Agra, patch by Salvatore Sanfilippo) * [NEW] Log offending memory access address on SIGSEGV/SIGBUS (Salvatore Sanfilippo) https://raw.githubusercontent.com/antirez/redis/2.8/00-RELEASENOTES No config changes.
-
Kirill Smelkov authored
Ruby 2.1.8 contains security and other bugfixes https://www.ruby-lang.org/en/news/2015/12/16/ruby-2-1-8-released/
-
- 24 Feb, 2016 2 commits
-
-
Kirill Smelkov authored
@rafael says frontend infrastructure is not yet ready to handle slave requests for frontends which come with lab.nexedi.com frontend SR URLs. So revert apache-frontend-URL related part of 86deb9c6 (*: slapos.git moved to https://lab.nexedi.com/nexedi/slapos.git) back for now. /cc @jp /reviewed-by @rafael /reviewed-on nexedi/slapos!52
-
Kirill Smelkov authored
86deb9c6 (*: slapos.git moved to https://lab.nexedi.com/nexedi/slapos.git) went over whole tree and updated slapos.git URL but when changing non-top-software.cfg-like files forgot to update their md5sum in software releases. Fixes started to appear - e.g. 8b1496c3 (kvm: fix md5sum, thanks @alain.takoudjou), but generally the whole tree remains more-or-less broken. Fix it. (not tested - manually checked files and updated md5sums) /reported-by @rafael
-
- 23 Feb, 2016 1 commit
-
-
Alain Takoudjou authored
-
- 22 Feb, 2016 1 commit
-
-
Cédric Le Ninivin authored
-
- 21 Feb, 2016 1 commit
-
-
https://lab.nexedi.com/nexedi/slapos.gitKirill Smelkov authored
This updates links to slapos.git in the tree to point to new location. We do so whole-tree except one place in stack/monitor/ : [download-monitor-static] recipe = hexagonit.recipe.download url = http://git.erp5.org/gitweb/slapos.git/snapshot/930be99041ea26b7b1186830e5eb56ef0acc1bdf.tar.gz ... (see d8800c0b "monitor: Download statics files from snapshot") The reason we do not update that link yet, is that 930be99041ea26b7b1186830e5eb56ef0acc1bdf is a tree object and gitlab does not allow to dowload tree object as archives (yet ?) So for now that link stays unconverted - and we'll think how to do with it.
-
- 19 Feb, 2016 2 commits
-
-
Vincent Pelletier authored
-
Ivan Tyagov authored
Fix image display on jupyter This fix is for bug https://nexedi.erp5.net/bug_module/20160212-76EAAC/view?ignore_layout:int=1 where the image base64 string was only showing. The error in this case was that the `mime_type` of content code_result was not being updated by the kernel before display. Reported by : @Tyagov Please review: @Tyagov @kirr For testing, you can use this jupyter instance with updated kernel running : https://[2001:67c:1254:e:8b::335d]:8888/tree There are also some example notebooks in the aforementioned jupyter. See merge request !47
-
- 18 Feb, 2016 2 commits
-
-
Rafael Monnerat authored
-
Ayush Tiwari authored
This fix is for bug https://nexedi.erp5.net/bug_module/20160212-76EAAC/view?ignore_layout:int=1 where the image base64 string was only shoeing. The error in this case was that the mime_type of content code_result was not being updated by the kernel before display. Reported by : @ivan
-
- 17 Feb, 2016 4 commits
-
-
Kirill Smelkov authored
To pick up kirr/gitlab-ce@32fa1180 /cc @kazuhiko, @jerome /reviewed-by TrustMe
-
Kirill Smelkov authored
6a4e45c5 (gitlab: Sync sidekiq service launch with upstream) claimed to sync sidekiq startup with upstream, but missed one upstream change in between 8.2 and 8.4: https://gitlab.com/gitlab-org/omnibus-gitlab/commit/2eb7634f My bad - I should have reviewed git log for https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-cookbooks/gitlab/templates/default/sv-sidekiq-run.erb and I did not noticed that change because I did not and just compared queues list visually. Pick it up. /cc @kazuhiko, @jerome /reviewed-by TrustMe (I hope)
-
Rafael Monnerat authored
-
Kirill Smelkov authored
This brings slapos gitlab port up to date with current stable gitlab version 8.4, and teaches Unicorn startup script to wait a bit for PostgreSQL to start and be ready, before unicorn startup proceeds. /cc @kazuhiko /somewhat-reviewed-by @jerome /reviewed-on nexedi/slapos!44
-
- 16 Feb, 2016 3 commits
-
-
Alain Takoudjou authored
This changes were squashed into a single commit and it includes: - install slapos_configurator by default - Allow define ssl authentication for a certain zope family - Allow define custom zope path per zope family Those changes are originally written by Alain Takoudjou and rewrited by Rafael Monnerat
-
Kirill Smelkov authored
To pick up kirr/gitlab-ce@a5965b54.
-
Rafael Monnerat authored
The local changes are not yet generic enough to be shared among stack, so Introduce local changes here better
-
- 15 Feb, 2016 5 commits
-
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
There is no strong reason to use git.erp5.org to test code anymore
-
Rafael Monnerat authored
slapos.package is not an egg anymore, it's implementation was replaced by the usage of ansible with playbooks.
-
Rafael Monnerat authored
-
- 13 Feb, 2016 1 commit
-
-
Kirill Smelkov authored
As it was outlined in 5a744de7 (gitlab: Compile assets on instantiation and make sure DB is properly setup/migrated before unicorn runs) we are performing DB initialization and migration in pre-action as part of unicorn startup script. But that currently has one drawback: if all services start at the same time - e.g. both PostgreSQL and Unicorn - and that is a common scenario when SR is compiled and instantiated / started, PostgreSQL is usually not yet ready to process queries from Unicorn startup script, and first-time Unicorn startup fails. Until now this problem was workarounded by manually starting unicorn second time - after some time postgresql is started and ready. But why do it manually, if we can do the same logic automatically. So fix it: in Unicorn startup script wait a bit (up to 5 seconds) for PostgreSQL to become ready. /cc @kazuhiko, @jerome
-
- 12 Feb, 2016 2 commits
-
-
iv authored
This is a SR to build NayuOS binary images. More info on https://www.nayuos.com and in the README. Merging this recipe from a standalone repository was a decision made together with @kirr and @vpelletier.
-
iv authored
-
- 11 Feb, 2016 11 commits
-
-
Kirill Smelkov authored
Even though we do not use LFS objects, builds and build artifacts, gitlab backups corresponding directories and recreates them upon restore. Current state is: the directories are living under Rails root - that is in our gitlab-work/ inside instance, and since gitlab-work is recreated almost on every re-instantiation if we'll have some content in that directories - it will be lost. Don't allow even a chance for that to happen and move what is designed to hold data to under var/ . NOTE we create shared/lfs-objects/ and shared/artifacts/ because if we do not have this dirs, gitlab backup fails. Upstream code just assumes the directories are there. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
Upstream added `pages` and `elasticsearch` queues to sidekiq https://gitlab.com/gitlab-org/omnibus-gitlab/commit/be6844ff https://gitlab.com/gitlab-org/omnibus-gitlab/commit/801d6ed7 but since those queues are used for EE-only services we do not enable them. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
As gitlab-workhorse is now serving everything, it proxies unknown-to-it requests to unicorn, and that returns redirect to /users/sign_in for /non-existent, not 403. Adjust the promise and just verify whether we can get /static.css NOTE nginx promise now effectively depends on gitlab-workhorse being up and running - because nginx is now configured to be only an SSL terminator and all requests processing is done by gitlab-workhorse and services below it. If in the future we'll need a pure nginx-is-up promise, we can introduce something to nginx config and verify that particular http endpoint. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
add `-documentRoot ...` argument to gitlab-workhorse start as upstream started to do: https://gitlab.com/gitlab-org/omnibus-gitlab/commit/d769f751 ( gitlab-workhorse now needs to know where document root is as it now serves all content - e.g. static files too this option was introduced here: https://gitlab.com/gitlab-org/gitlab-workhorse/commit/1a7009e4 ) /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
I manually reviewed files/gitlab-config-template/gitlab.rb.template files/gitlab-cookbooks/gitlab/attributes/default.rb from omnibus-gitlab 8.4.2+ce.0-3-g68d5ee8 and picked up changes: - unicorn OOM killer memory limits were raised up (because gitlab is now more memory hungry according to talks on gitlab.com) https://gitlab.com/gitlab-org/omnibus-gitlab/commit/f8ee4a19 - there is no default limit for nginx client_max_body_size - it just goes to gitlab-workhorse as is at any size https://gitlab.com/gitlab-org/omnibus-gitlab/commit/78862837 /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
Direct merge for gitconfig.erb from omnibus-gitlab did not brought up updates. pack.threads=1 and receive.fsckObjects=true picked up from https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-cookbooks/gitlab/attributes/default.rb in 264d785a stay the same. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
No changes. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
- there is a section for gitlab pages, which we stub-out; - there is no longer a need to add /raw/... handling to nginx - as now nginx is just an SSL terminator for gitlab-workhorse, all URL handling is done inside gitlab-workhorse and is dealt with ok by our patches. - as now nginx does not directly connect to unicorn, there is no need to pass unicorn section to nginx's template. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
Like wih gitlab configs, this does only pure merge. We will slaposify / adjust to updates in the following patches. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
Slapos'ify config updates brought by sync with omnibus-gitlab (see merge in the previous patch). Changes: - default visibility levels gone away (see merge commit and https://gitlab.com/gitlab-org/omnibus-gitlab/commit/b5ebbab3 ) - there are new settings for GitLab Pages and Elasticsearch, which are EE only and thus we do not support them. - there are new settings for auxiliary cron-like jobs, which we do not support for now, since they are used either for CI (not supported by us) or EE features. Configuration files that were synced, but did not changed are also marked as updated, so it is easier to track their changes to upstream in the future. /cc @kazuhiko, @jerome
-
Kirill Smelkov authored
This does only pure merge. We will slaposify / adjust config and corresponding md5sum in the following patches. /cc @kazuhiko, @jerome
-