A large repository git push is timing out during "Validating diffs' file paths"
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The is is a follow-up to A large repository git push is timing out durin... (gitaly#3751 - closed) for a different customer.
- Changes were made around 14.10 - 15.0 to help with this, but here's an example of it still failing on GitLab.com with GitLab Enterprise Edition 15.7.0-pre c7818943
- GitLab team members can read more in the ticket.
- Customer is trying to migrate a very large repo to GitLab.com - the repo is gigabytes, and there's a lot of LFS data as well.
json.grpc.method: PreReceiveHook
json.level: warning
json.msg: stopping transaction because pre-receive hook failed
json.error:
GitLab: Push operation timed out
Timing information for debugging purposes:
[snip] - - - - - - - - - - - - [roughly 10,000 refs]
Checking if you are allowed to push... (5.87ms)
Checking if default branch is being deleted... (0.02ms)
Validating diffs' file paths... (3.29ms)
Checking if you are allowed to push... (0.17ms)
Checking if default branch is being deleted... (0.02ms)
Validating diffs' file paths... (cancelled)
All the customer reported is as follows; it's possible the timeout error was also returned to the client (I've asked on the ticket) but the other errors might have swamped the console.
! [remote rejected] foo.1 -> foo.1 (pre-receive hook declined)
! [remote rejected] foo.2 -> foo.2 (pre-receive hook declined)
! [remote rejected] foo.3 -> foo.3 (pre-receive hook declined)
! [remote rejected] foo.4 -> foo.4 (pre-receive hook declined)
They had previously had issues with pre-rec hook failing because of missing LFS objects, and so concluded it was the same issue.
Edited by 🤖 GitLab Bot 🤖