push changes to a GitLab repo returns 411 error

Open
#1,448 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, git, gitlab
Domain
backend

Research direction

Start by reproducing the push against the reported self-hosted GitLab 8.8.2 setup with Libgit2sharp 0.24.0.0, then trace the failure through git_remote_push and Ensure.ZeroResult(res), using reference #905 for context. Done means identifying why the push produces HTTP 411 and documenting or testing a confirmed resolution.

Written by the indexing model from the issue text.

Description

Does anyone encounter that push change to a gitlab repo and returns "Request failed with status code: 411" error?

I hava a reference #905 comment on GitHub, but still getting the same error when debugging it gets to git_remote_push which returns res = -1 and Ensure.ZeroResult(res) returns 411 error.

In addition, we are running gitlab (v8.8.2) on our own server. Use the Libgit2sharp version 0.24.0.0

Dominant language
C#
Stars
3.5k
Forks
925
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libgit2/libgit2sharp

All issues in libgit2/libgit2sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.