GIT_EBUFS error being thrown on successful push the AWS CodeCommit repository.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.8k
- Forks
- 704
- PR merge metrics
- No merged PRs in 30d
Description
After pushing to changes to a git repository on AWS CodeCommit using SSH based credentials, an error is thrown, however the push to AWS is successful. The error message is
Error: Method push has thrown an error.
and the error number is {"errno":-6}, which I've tracked back to GIT_EBUFS found here https://github.com/nodegit/nodegit/blob/44779afd0d460011e13a5cba9a47a48119aa472e/vendor/libgit2/include/git2/errors.h#L28
I've got a reproduction case here : https://gist.github.com/Murcho/fcba744b2870fa38531f
Requirements for the case are:
- Set up an AWS CodeCommit account.
- Create an IAM user account.
- Follow this guide for setting up the AWS IAM account with your SSH keys http://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-without-cli.html
- Add 2 permissions to the IAM user : AWSCodeCommitFullAccess and IAMUserSSHKeys.
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 running the linked reproduction case against an AWS CodeCommit repository configured with the documented SSH and IAM setup. Inspect the GIT_EBUFS definition in vendor/libgit2/include/git2/errors.h and compare the push result with the reported error. Done means a successful CodeCommit push no longer reports Method push has thrown an error or errno -6.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git, javascript, node.js
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100