Update User.NumRepos atomically in createRepository (#7493)
The update call on the user call races if there is more than one repository creation concurrently, leading to incorrect count of repos. Split things in two, so that we call the update for last visibility (which isn't problematic if it races, since it can only ever be best-effort anyway). This way we can atomically increment the count of repos.tokarchuk/v1.17
parent
0e2996caa1
commit
361607d831
Loading…
Reference in new issue