forks/forgejo
1
0
Fork 0
Code Releases Activity

Fix DeleteCollaboration transaction behaviour (#28886)

Browse source 
The method can't be called with an outer transaction because if the user
is not a collaborator the outer transaction will be rolled back even if
the inner transaction uses the no-error path.

`has == 0` leads to `return nil` which cancels the transaction. A
standalone call of this method does nothing but if used with an outer
transaction, that will be canceled.
This commit is contained in:
KN4CK3R 2024-01-22 08:19:56 +01:00 committed by GitHub
parent 23efd9d278
commit 8e9b6817bc
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
services/repository/collaboration.go
View file

@ -26,9 +26,12 @@ func DeleteCollaboration(ctx context.Context, repo *repo_model.Repository, uid i
} }
defer committer.Close() defer committer.Close()
if has, err := db.GetEngine(ctx).Delete(collaboration); err != nil || has == 0 { if has, err := db.GetEngine(ctx).Delete(collaboration); err != nil {
return err return err
} else if err = access_model.RecalculateAccesses(ctx, repo); err != nil { } else if has == 0 {
return committer.Commit()
}
if err = access_model.RecalculateAccesses(ctx, repo); err != nil {
return err return err
} }