libgit2 / libgit2/libgit2sharp
push changes to a GitLab repo returns 411 error
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- csharp, git, gitlab
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100