- 13 Jan, 2016 23 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
-
Yorick Peterse authored
See merge request !2406
-
Douwe Maan authored
Fix #9963 reference_filter "Encoding::CompatibilityError" bug with some complex URL; https://github.com/gitlabhq/gitlabhq/pull/9964 @DouweM See merge request !2383
-
Jason Lee authored
-
Douwe Maan authored
Extend projects API with CI data Reference #4264 See merge request !2303
-
Douwe Maan authored
enable milestone filter to stick See merge request !2241
-
Yorick Peterse authored
Sampling data at a fixed interval means we can potentially miss data from events occurring between sampling intervals. For example, say we sample data every 15 seconds but Unicorn workers get killed after 10 seconds. In this particular case it's possible to miss interesting data as the sampler will never get to actually submitting data. To work around this (at least for the most part) the sampling interval is randomized as following: 1. Take the user specified sampling interval (15 seconds by default) 2. Divide it by 2 (referred to as "half" below) 3. Generate a range (using a step of 0.1) from -"half" to "half" 4. Every time the sampler goes to sleep we'll grab the user provided interval and add a randomly chosen "adjustment" to it while making sure we don't pick the same value twice in a row. For a specified timeout of 15 this means the actual intervals can be anywhere between 7.5 and 22.5, but never can the same interval be used twice in a row. The rationale behind this change is that on dev.gitlab.org I'm sometimes seeing certain Gitlab::Git/Rugged objects being retained, but only for a few minutes every 24 hours. Knowing the code of Gitlab and how much memory it uses/leaks I suspect we're missing data due to workers getting terminated before the sampler can write its data to InfluxDB.
-
Yorick Peterse authored
-
Dmitriy Zaporozhets authored
merge request close message moved and merge request now refered by `!`. Fixes #4161 ![Screen_Shot_2016-01-12_at_8.38.57_AM](/uploads/9390ce0ebd1d14bfc83130ff4913a823/Screen_Shot_2016-01-12_at_8.38.57_AM.png) See merge request !2387
-
Dmitriy Zaporozhets authored
Disable colorization if STDOUT is not a tty Closes #6118 See merge request !2403
-
Dmitriy Zaporozhets authored
Block the reported user before destroying the record This is intended to prevent the user from creating new objects while the transaction that removes them is being run, resulting in objects with nil authors which can then not be edited. See https://gitlab.com/gitlab-org/gitlab-ce/issues/7117 See merge request !2402
-
Dmitriy Zaporozhets authored
Make sure time_ago_with_tooltip is using a Time object Somehow this test existed on EE but not in CE, so it started failing after a bad CE-to-EE merge. See merge request !2398
-
Dmitriy Zaporozhets authored
Comment and close button does not submit comment See merge request !2399
-
https://github.com/tbeadle/gitlabhqDmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Include the user_id in user_*_team system hooks.
-
Stan Hu authored
Mention channel/key bug in irkerd docs
-
Robert Speicher authored
It patches core classes (such as String) to add colorization methods like `red` which we can't disable the same way we can with the Colorization gem.
-
Robert Speicher authored
-
Robert Speicher authored
This is intended to prevent the user from creating new objects while the transaction that removes them is being run, resulting in objects with nil authors which can then not be edited. See https://gitlab.com/gitlab-org/gitlab-ce/issues/7117
-
Jacob Schatz authored
-
Jacob Schatz authored
-
- 12 Jan, 2016 17 commits
-
-
Robert Speicher authored
Prepare Installation and Update docs for 8.4 RC1 [ci skip] See merge request !2401
-
Robert Speicher authored
[ci skip]
-
Landon authored
Per this issue: https://gitlab.com/esr/irker/issues/2 A documentation update was added to irkerd (https://gitlab.com/esr/irker/commit/190808c37d4ab5f0f16fe35352ff36863c2732d5) but the bug is still there. Making a note of it here could save someone a lot of hassle. This could probably be worded better if someone else wants to take a stab at it.
-
Robert Speicher authored
Revert "Remove the `:coffee` and `:coffeescript` Haml filters" This reverts commit ae7de2f8. Several files in EE still use the `:coffeescript` filter and I don't have time to fix them before the CE-to-EE merge. See https://gitlab.com/gitlab-org/gitlab-ee/builds/553647 I will reintroduce this change in a future MR. See merge request !2400
-
Robert Speicher authored
This reverts commit ae7de2f8.
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Greg Smethells authored
-
Jacob Schatz authored
-
Jacob Schatz authored
-
Robert Speicher authored
Somehow this test existed on EE but not in CE, so it started failing after a bad CE-to-EE merge.
-
Dmitriy Zaporozhets authored
Change milestone close notice copy. Closes #6051 See merge request !2372
-