delta/gitlab/gitlab-ce.git/app/services/users, branch update-singleton-pattern-docs gitlab.com: gitlab-org/gitlab-ce.git Fix logic in Users::CreateService broken by the fix for OAuth users 2017-04-26T08:08:44+00:00 Rémy Coutable remy@rymai.me 2017-04-26T07:54:33+00:00 aa54bb7e5a247e98efa95ad810503579eb3d0cbc Signed-off-by: Rémy Coutable <remy@rymai.me> 
Signed-off-by: Rémy Coutable <remy@rymai.me>
Ensures that OAuth/LDAP/SAML users don't need to be confirmed 2017-04-26T08:08:44+00:00 Rémy Coutable remy@rymai.me 2017-04-25T19:51:36+00:00 fa01c373594203278a5809c7bae800d97e224f64 Signed-off-by: Rémy Coutable <remy@rymai.me> 
Signed-off-by: Rémy Coutable <remy@rymai.me>
Fix OAuth, LDAP and SAML SSO when regular sign-ups are disabled 2017-04-25T02:27:39+00:00 Douwe Maan douwe@selenight.nl 2017-04-24T21:12:14+00:00 d7e2ac729317ace2ccf0203663637ba32f328d1a 






Move records to the ghost user in a transaction.
2017-04-24T06:46:10+00:00

Timothy Andrew
mail@timothyandrew.net

2017-04-21T05:55:24+00:00

133f00bedd990e4220cbd89cbfbe7f69e98c0c76

- While deleting a user, some of the user's associated records are moved to the
  ghost user so they aren't deleted. The user is blocked before these records
  are moved, to prevent the user from creating new records while the migration
  is happening, and so preventing a data race.

- Previously, if the migration failed, the user would _remain_ blocked, which is
  not the expected behavior. On the other hand, we can't just stick the block +
  migration into a transaction, because we want the block to be committed before
  the migration starts (for the data race reason mentioned above).

- One solution (implemented in this commit) is to block the user in a parent
  transaction, migrate the associated records in a nested sub-transaction, and
  then unblock the user in the parent transaction if the sub-transaction fails.





- While deleting a user, some of the user's associated records are moved to the
  ghost user so they aren't deleted. The user is blocked before these records
  are moved, to prevent the user from creating new records while the migration
  is happening, and so preventing a data race.

- Previously, if the migration failed, the user would _remain_ blocked, which is
  not the expected behavior. On the other hand, we can't just stick the block +
  migration into a transaction, because we want the block to be committed before
  the migration starts (for the data race reason mentioned above).

- One solution (implemented in this commit) is to block the user in a parent
  transaction, migrate the associated records in a nested sub-transaction, and
  then unblock the user in the parent transaction if the sub-transaction fails.







Merge branch 'usage-ping-port' into 'master'

2017-04-19T14:48:31+00:00

Sean McGivern
sean@mcgivern.me.uk

2017-04-19T14:48:31+00:00

40a972057da58dd5c15cf0f0b2952f264dba0076


Usage ping port

Closes #27750

See merge request !10481





Usage ping port

Closes #27750

See merge request !10481






Hard delete users' associated records deleted from AbuseReports
2017-04-16T15:36:33+00:00

Stan Hu
stanhu@gmail.com

2017-04-16T15:21:40+00:00

60eee739f040e997d6dac3f4e21ef90daa6c7f30

In the case of spammers, we really want a hard delete to avoid retaining spam.

Closes #31021





In the case of spammers, we really want a hard delete to avoid retaining spam.

Closes #31021







Add a new Gitlab::UserActivities class to track user activities
2017-04-14T13:20:55+00:00

Rémy Coutable
remy@rymai.me

2017-03-07T18:34:43+00:00

cfe19b795e076b73df75ee57839640667283651c

This new class uses a Redis Hash instead of a Sorted Set.

Signed-off-by: Rémy Coutable <remy@rymai.me>





This new class uses a Redis Hash instead of a Sorted Set.

Signed-off-by: Rémy Coutable <remy@rymai.me>







Remove user activities table and use redis instead of PG for recording activities
2017-04-14T13:20:55+00:00

James Lopez
james@jameslopez.es

2016-11-25T16:10:25+00:00

3cb84e06b7a118fb46b4e1e0d4885026c9d4a4d1

Refactored specs and added a post deployment migration to remove the activity users table.





Refactored specs and added a post deployment migration to remove the activity users table.







Add user activity service and spec. Also added relevant - NOT offline - migration
2017-04-14T13:20:55+00:00

James Lopez
james@jameslopez.es

2016-10-05T14:41:32+00:00

2951a8543ef97ceb1bcaca5f5140d822729c950b

It uses a user activity table instead of a column in users.
Tested with mySQL and postgreSQL





It uses a user activity table instead of a column in users.
Tested with mySQL and postgreSQL







Implement Users::BuildService
2017-04-13T10:02:59+00:00

geoandri
geoandri@gmail.com

2017-04-13T08:47:52+00:00

defbff482d537975e8493c4f687e195bfd3d3919