- 02 7月, 2016 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Stan Hu 提交于
If a site specifies a relative URL root, emoji files would omit the path from the URL, leading to lots of 404s. Closes #15642
-
- 01 7月, 2016 2 次提交
-
-
由 James Lopez 提交于
-
由 Eric K Idema 提交于
This stands as an alternative to using OAuth to access a user's Github repositories. This is setup in such a way that it can be used without OAuth configuration. From a UI perspective, the how to import modal has been replaced by a full page, which includes a form for posting a personal access token back to the Import::GithubController. If the user has logged in via GitHub, skip the Personal Access Token and go directly to Github for an access token via OAuth.
-
- 30 6月, 2016 5 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Stan Hu 提交于
-
由 Stan Hu 提交于
If Redis were not running or USE_DB were set to false, the application settings retrieval would fail completely. This change only attempts to use the cache if the system actually wants to connect to the DB and rescues any failures in talking to Redis. Closes #17557
-
- 29 6月, 2016 4 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 James Lopez 提交于
-
由 James Lopez 提交于
-
由 Z.J. van de Weg 提交于
-
- 28 6月, 2016 7 次提交
-
-
由 Yorick Peterse 提交于
Process.clock_gettime allows getting the real time in nanoseconds as well as allowing one to get a monotonic timestamp. This offers greater accuracy without the overhead of having to allocate a Time instance. In general using Time.now/Time.new is about 2x slower than using Process.clock_gettime(). For example: require 'benchmark/ips' Benchmark.ips do |bench| bench.report 'Time.now' do Time.now.to_f end bench.report 'clock_gettime' do Process.clock_gettime(Process::CLOCK_MONOTONIC, :millisecond) end bench.compare! end Running this benchmark gives: Calculating ------------------------------------- Time.now 108.052k i/100ms clock_gettime 125.984k i/100ms ------------------------------------------------- Time.now 2.343M (± 7.1%) i/s - 11.670M clock_gettime 4.979M (± 0.8%) i/s - 24.945M Comparison: clock_gettime: 4979393.8 i/s Time.now: 2342986.8 i/s - 2.13x slower Another benefit of using Process.clock_gettime() is that we can simplify the code a bit since it can give timestamps in nanoseconds out of the box.
-
由 Paco Guzman 提交于
In any case if just want the value which is always ‘gitlab’ require 'benchmark/ips' Project.first # To load database things GitlabIssueTrackerService.first # To load database things Benchmark.ips do |x| x.config(:time => 5, :warmup => 2) x.report("current") do Project.new.default_issue_tracker.to_param end x.report("") do 'gitlab' end x.compare! end Calculating ------------------------------------- current 4.000 i/100ms 30.938k i/100ms ------------------------------------------------- current 47.298 (±10.6%) i/s - 232.000 4.366M (±20.9%) i/s - 17.202M Comparison: : 4366456.0 i/s current: 47.3 i/s - 92318.26x slower
-
由 Z.J. van de Weg 提交于
Depends on the changes in Workhorse (gitlab-org/gitlab-workhorse!48).
-
由 http://jneen.net/ 提交于
-
由 http://jneen.net/ 提交于
-
由 http://jneen.net/ 提交于
-
由 http://jneen.net/ 提交于
paired with @stanhu
-
- 27 6月, 2016 1 次提交
-
-
由 James Lopez 提交于
-
- 24 6月, 2016 1 次提交
-
-
由 James Lopez 提交于
Fix tmp file being deleted after the request plus some cleanup and improved erroring for this situation
-
- 23 6月, 2016 2 次提交
-
-
由 Paco Guzman 提交于
-
由 Drew Blessing 提交于
-
- 22 6月, 2016 1 次提交
-
-
由 James Lopez 提交于
-
- 21 6月, 2016 6 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
This commit builds on the groundwork in ee008e300b1ec0abcc90e6a30816ec0754cea0dd, which refactored the backend so the same code could be used for new dropdowns. In this commit its used for templates for the `.gitlab-ci.yml` files.
-
由 ZJ van de Weg 提交于
-
- 20 6月, 2016 2 次提交
-
-
由 James Lopez 提交于
-
由 James Lopez 提交于
-
- 19 6月, 2016 1 次提交
-
-
由 Stan Hu 提交于
When using #XYZ in Markdown text, if XYZ exceeds the maximum value of a signed 32-bit integer, we get an exception when the Markdown render attempts to run `where(iids: XYZ)`. Introduce a method that will throw out out-of-bounds values. Closes #18777
-
- 18 6月, 2016 4 次提交
-
-
由 Rémy Coutable 提交于
This is a try for a new approach to put the access checks at the service level. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
-
由 Yorick Peterse 提交于
Previously we'd create a separate Metric instance for every method call that would exceed the method call threshold. This is problematic because it doesn't provide us with information to accurately get the _total_ execution time of a particular method. For example, if the method "Foo#bar" was called 4 times with a runtime of ~10 milliseconds we'd end up with 4 different Metric instances. If we were to then get the average/95th percentile/etc of the timings this would be roughly 10 milliseconds. However, the _actual_ total time spent in this method would be around 40 milliseconds. To solve this problem we now create a single Metric instance per method. This Metric instance contains the _total_ real/CPU time and the call count for every instrumented method.
-
由 Paco Guzman 提交于
-
- 17 6月, 2016 2 次提交
-
-
由 Yorick Peterse 提交于
This changes update_column_in_batches to ensure it always updates all rows now. These changes also allow for an extra SELECT query to be removed, nor does it use the row count for determining offsets and the likes; instead it's only used to determine the batch size.
-
由 James Lopez 提交于
-