- 09 Dec, 2015 1 commit
-
-
Stan Hu authored
-
- 07 Dec, 2015 1 commit
-
-
Robert Speicher authored
-
- 25 Nov, 2015 1 commit
-
-
Robert Speicher authored
-
- 18 Nov, 2015 3 commits
-
-
Yorick Peterse authored
This method can be used to filter projects to those visible to a given user.
-
Douwe Maan authored
-
Douwe Maan authored
-
- 17 Nov, 2015 1 commit
-
-
Douwe Maan authored
-
- 16 Nov, 2015 1 commit
-
-
Marin Jankovski authored
-
- 13 Nov, 2015 1 commit
-
-
Kamil Trzcinski authored
- Enable CI by default for all new projects
-
- 05 Nov, 2015 2 commits
-
-
Kamil Trzcinski authored
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 03 Nov, 2015 1 commit
-
-
James Lopez authored
refactored permissions and added update_project_member ability logic. Also refactored owner methods to a concern.
-
- 21 Oct, 2015 2 commits
-
-
Artem V. Navrotskiy authored
-
Douwe Maan authored
-
- 20 Oct, 2015 1 commit
-
-
Douwe Maan authored
-
- 14 Oct, 2015 2 commits
-
-
Valery Sizov authored
-
Kamil Trzcinski authored
-
- 08 Oct, 2015 1 commit
-
-
Yorick Peterse authored
By using a JOIN we can remove the need for using 2 separate queries to find a project by its namespace. Combined with an index (only needed for PostgreSQL) this reduces the query time from ~245 ms (~520 ms for the first call) down to roughly 10 ms (~15 ms for the first call).
-
- 06 Oct, 2015 1 commit
-
-
Yorick Peterse authored
This changes the query to use a COUNT nested in an INNER JOIN, instead of a COUNT plus a GROUP BY. There are two reasons for this: 1. Using a COUNT in an INNER JOIN can be quite a bit faster. 2. The use of a GROUP BY means that method calls such as "any?" (and everything else that calls "count") operate on a Hash that counts the amount of notes on a per project basis, instead of just counting the total amount of projects. The query has been moved into Project.trending as its logic is simple enough. As a result of this testing the TrendingProjectsFinder class simply involves testing if the right methods are called, removing the need for setting up database records.
-
- 05 Oct, 2015 1 commit
-
-
Kamil Trzcinski authored
-
- 03 Oct, 2015 1 commit
-
-
Guilherme Garnier authored
-
- 02 Oct, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 01 Oct, 2015 1 commit
-
-
Valery Sizov authored
-
- 29 Sep, 2015 6 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 25 Sep, 2015 2 commits
-
-
Stan Hu authored
-
Stan Hu authored
A race condition existed between when Rails committed the `import_status` to `started` and when the Sidekiq worker forked a project. If this fork was quick, it's possible that the worker would attempt to move into the `finished` state before the `started` state took effect. As mentioned in https://github.com/mperham/sidekiq/wiki/Problems-and-Troubleshooting#cannot-find-modelname-with-id12345, we should delay the worker to ensure the DB has a chance to update. Closes #2736
-
- 23 Sep, 2015 3 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 18 Sep, 2015 2 commits
-
-
Kamil Trzcinski authored
-
Francesco Levorato authored
-
- 16 Sep, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 11 Sep, 2015 1 commit
-
-
Stan Hu authored
Use import_status to track async import status and give feedback to the user Closes #2388 Closes #2400
-
- 09 Sep, 2015 1 commit
-
-
Jared Szechy authored
-
- 03 Sep, 2015 1 commit
-
-
Valery Sizov authored
-