Skip to content

Repository branches can trigger Gitlab::Git::CommandError: 4:Deadline Exceeded

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Sentry Link: https://sentry.gitlab.net/gitlab/gitlabcom/issues/1048981/ https://sentry.gitlab.net/gitlab/gitlabcom/issues/1048726/

GRPC::DeadlineExceeded: 4:Deadline Exceeded
  grpc/generic/active_call.rb:31:in `check_status'
    fail GRPC::BadStatus.new_status_exception(
  grpc/generic/active_call.rb:181:in `attach_status_results_and_complete_call'
    recv_status_batch_result.check_status
  grpc/generic/active_call.rb:170:in `receive_and_check_status'
    attach_status_results_and_complete_call(batch_result)
  grpc/generic/active_call.rb:338:in `each_remote_read_then_finish'
    receive_and_check_status
  gitlab/gitaly_client/ref_service.rb:277:in `each'
    response.flat_map do |message|
...
(144 additional frame(s) were not displayed)

Gitlab::Git::CommandError: 4:Deadline Exceeded
  gitlab/git/wraps_gitaly_errors.rb:13:in `rescue in wrapped_gitaly_errors'
    raise Gitlab::Git::CommandError.new(e)
  gitlab/git/wraps_gitaly_errors.rb:6:in `wrapped_gitaly_errors'
    def wrapped_gitaly_errors(&block)
  gitlab/metrics/instrumentation.rb:161:in `block in wrapped_gitaly_errors'
    .measure { super }
  gitlab/metrics/method_call.rb:36:in `measure'
    retval = yield
  gitlab/metrics/instrumentation.rb:161:in `wrapped_gitaly_errors'
    .measure { super }
...
(135 additional frame(s) were not displayed)

Gitlab::Git::CommandError: 4:Deadline Exceeded
Edited by 🤖 GitLab Bot 🤖