- 19 7月, 2017 4 次提交
-
-
由 Paweł Chojnacki 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 18 7月, 2017 10 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
-
由 Grzegorz Bizon 提交于
-
由 Andrew Newdigate 提交于
-
由 http://jneen.net/ 提交于
-
由 http://jneen.net/ 提交于
-
由 http://jneen.net/ 提交于
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
We also try to use instance variable to cache the result if RequestStore is not available, so we could keep the same logic, using the same cache key. Also introduce a way to specify method specific cache key
-
- 17 7月, 2017 6 次提交
-
-
由 Lin Jen-Shin 提交于
I don't like the idea of `RequestStore` at all, because it's just a global state which shouldn't be used at all. But we have a number of places calling `ProtectedBranch.protected?` and `ProtectedTag.protected?` in a loop for the same user, project, and ref whenever we're checking against if the jobs for a given pipeline is accessible for a given user. This means we're effectively making N queries for the same thing over and over. To properly fix this, we need to change how we check the permission, and that could be a huge work. To solve this quickly, adding a cache layer for the given request would be quite simple to do. We're already doing this in Commit#author, and this is extending that idea and make it generalized.
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Grzegorz Bizon 提交于
Simply re-raise an exception when it occurs, but guarantee that no background migration is lost in the process.
-
由 Rémy Coutable 提交于
If we don't expire the cached user IDs, the list of IDs would become outdated when a new member is added, or when a member ios removed from the allowed group. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
It also makes it possible to gracefully retry a migration in order to avoid problems like deadlocks.
-
- 15 7月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 14 7月, 2017 10 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
由 Grzegorz Bizon 提交于
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
由 Grzegorz Bizon 提交于
We first pop a job from the Sidekiq queue / scheduled set and only if this has been successfully deleted we process the job. This makes it possible to minimize a possibility of a race condition happening.
-
由 Stan Hu 提交于
Somehow Rails.cache.fetch occasionally returns `nil` values, which causes this endpoint to crash. Closes #35094
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
- 13 7月, 2017 6 次提交
-
-
由 Robin Bobbitt 提交于
When sign-in is disabled: - skip password expiration checks - prevent password reset requests - don’t show Password tab in User Settings - don’t allow login with username/password for Git over HTTP requests - render 404 on requests to Profiles::PasswordsController
-
由 Jacob Vosmaer 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Pawel Chojnacki 提交于
+ fix tests after metrics rename
-
由 Jacob Vosmaer 提交于
-
- 12 7月, 2017 3 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Ben Kochie 提交于
Add `seconds` unit to latency metrics based on uptream naming convention[0]. [0]: https://prometheus.io/docs/practices/naming/#metric-names
-
由 Ben Kochie 提交于
* Follow Prometheus naming conventions[0]. * Simplify metrics by adding response lables to the histogram. * Use standard `http_request_duration_seconds_...` names for the histogram. [0]: https://prometheus.io/docs/practices/naming/#metric-names
-