Checkout step fails with credential problem

Since yesterday, our pipeline starts failing at checkout step.

Full log shows:

Using subcommand credential helper for git operations
Cloning git repository - https://github.com/foo/bar.git
Cloning into '.'...
remote: Enumerating objects: 35648, done.        
remote: Counting objects: 100% (1590/1590), done.        
remote: Compressing objects: 100% (176/176), done.        
remote: Total 35648 (delta 1498), reused 1435 (delta 1412), pack-reused 34058 (from 3)        
Receiving objects: 100% (35648/35648), 36.08 MiB | 46.35 MiB/s, done.
Resolving deltas: 100% (22865/22865), done.
Checking out branch
***fatal: could not read Username for 'https://github.com': No such device or address***
Downloading some-lfs-file (434 KB)
fatal: could not read Username for 'https://github.com': No such device or address
...
more error w.r.t git lfs
...

SSH into the box and I am able to checkout the repo using task-agent-subcommands/checkout cli (I assume this is what being used by the checkout step, based on the log)

Full cli path is /tmp/task-agent-subcommands/task-agent-subcommands/checkout/1.0.1707-88c193f/linux/amd64/checkout, hope the version info is helpful, if this is a new issue.

This might be a bug or a combination of behavior change and lfs issue with our issue. Difficult to know, without understanding how checkout works internally.

Thanks

after some trial and error, it seems that the git config could be wrong?

right now it is

credential.https://github.com/my-org/my-project.git.helper=/tmp/task-agent-subcommands/task-agent-subcommands/checkout/1.0.1707-88c193f/linux/amd64/checkout credentials

and updating it this would resolve the issue:

credential.https://github.com.helper=/tmp/task-agent-subcommands/task-agent-subcommands/checkout/1.0.1707-88c193f/linux/amd64/checkout credentials

I tried to overwrite the config before checkout, but unfortunately checkout step would revert my change

Hey, we just released a fix. Can you let me know if you’re still seeing the issue please

Can confirm the issue had been resolved.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.