- 27 7月, 2017 27 次提交
-
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
we need to store the keyid to be able to update the signature later in case the missing key is added later.
-
由 Alexis Reigel 提交于
as we write the cache in the gpg commit class already the read should also happen there. This also removes all logic from the main commit class, which just proxies the call to the Gpg::Commit now.
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
we store the result of the gpg commit verification in the db because the gpg verification is an expensive operation.
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
由 Kevin O'Connor 提交于
-
- 26 7月, 2017 2 次提交
-
-
由 Sean McGivern 提交于
Previously, we used Psych, which would: 1. Check if a string was encoded as binary, and not ASCII-compatible. 2. Add the !binary tag in that case. 3. Convert to base64. We need to do the same thing, using a new column in place of the tag.
-
由 Z.J. van de Weg 提交于
-
- 25 7月, 2017 3 次提交
-
-
由 Jarka Kadlecova 提交于
-
由 Bob Van Landuyt 提交于
-
由 Tim Zallmann 提交于
-
- 24 7月, 2017 2 次提交
-
-
由 Sean McGivern 提交于
The `members` table can have entries where `user_id: nil`, because people can invite group members by email. We never want to include those as members, because it might cause confusion with the anonymous (logged out) user.
-
由 Jarka Kadlecova 提交于
-
- 20 7月, 2017 3 次提交
-
-
由 Alexander Randa 提交于
-
由 Ryan Scott 提交于
Marking an issue as a duplicate will now also add an upvote on behalf of the author on the original issue.
-
由 Ryan Scott 提交于
-
- 19 7月, 2017 3 次提交
-
-
由 Lin Jen-Shin 提交于
I realized where the N+1 queries were actually coming from project.protected_branches, but how come we cannot preload this, or cache this at all? Then I found that this is somehow a Rails limitation. What we're doing before, eventually come to: project.protected_branches.matching But why it's not cached? (project.protected_branches.loaded? is always false) It's because matching is a class method, which is called on the proxy. In this case, Rails cannot cache the result. I don't know if this is possible to implement or not, because clearly this would require some tricks to implement class methods on associations. So instead, we could just pass project.protected_branches to ProtectedRef.matching, then it would work regularly. With this change, there's no more N+1 queries.
-
由 Dimitrie Hoekstra 提交于
-
由 Jarka Kadlecova 提交于
-