By using AWS re:Post, you agree to the Terms of Use
/CodeCommit Git Windows fatal: Failed to write item to store [0x6c6]/

CodeCommit Git Windows fatal: Failed to write item to store [0x6c6]

0

Is there a solution for the fatal message 0x6c6 that shows up in git-bash for Windows? It's annoying since it appears that operations continue normally other than the "fatal" part. My coworkers using Windows experience the same problem. I've included the full error along with the GIT_TRACE=1 info.

09:45:39.933420 run-command.c:654       trace: run_command: 'git credential-manager-core store'
09:45:40.042896 exec-cmd.c:237          trace: resolved executable dir: C:/Users/xxxxxxxx/AppData/Local/Programs/Git/mingw64/libexec/git-core
09:45:40.042896 git.c:748               trace: exec: git-credential-manager-core store
09:45:40.042896 run-command.c:654       trace: run_command: git-credential-manager-core store
fatal: Failed to write item to store. [0x6c6]
fatal: The array bounds are invalid

This is a newly setup Win10 Pro system. I'm using the following: git 2.36.1, Python 3.10.4, git-remote-codecommit 1.16, and we use a non AWS identity provider for SSO.

$ aws --version
aws-cli/2.6.3 Python/3.9.11 Windows/10 exe/AMD64 prompt/off

Here's ~/.gitconfig on the affected system.

[credential "url pointing to aws codecommit"]
    provider = generic
[protocol "codecommit"]
    allow = always

Here's part of the repo .git/config

[core]
    repositoryformatversion = 0
    filemode = false
    bare = false
    logallrefupdates = true
    symlinks = false
    ignorecase = true
[submodule]
    active = .
[remote "origin"]
    url = codecommit::region://repo-name
    fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
    remote = origin
    merge = refs/heads/master

Linux systems don't have this problem.

1 Answers
0

This is an issue with the git credential manager. You will need to update to the latest release. I recently confirmed this on a windows machine.

answered 2 months ago
  • I'm already running the lastest version of everything. Switching the credential manager to wincredman gives the same error and using dpapi causes a different error about paths.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions