You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
One of my colleagues is having an issue pulling the latest changes from one of our repositories.
This is the output they are getting.
--------------------------------------------------------------------------------------
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Password for 'https://username@Bitbucket.org': No such file or directory
Downloading Assets/Models/fbxmodel.FBX (85 KB)
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Password for 'https://username@Bitbucket.org': No such file or directory
Error downloading object: Assets/Models/fbxmodel.FBX (3d6ae29): Smudge error: Error downloading Assets/Models/fbxmodel.FBX (3d6ae2923a82e669dec834a830f120e548b3be97a126c429f47b7b69ce84465b): batch response: Git credentials for https://username@Bitbucket.org/company/projectname.git not found.Errors logged to D:\_GIT_Repository\project_directory\.git\lfs\logs\20210208T152402.2276423.log
Use `git lfs logs last` to view the log.error: external filter 'git-lfs filter-process' failed
fatal: Assets/Models/fbxmodel.FBX: smudge filter lfs failed
Completed with errors, see above.
---------------------------------------------------------------------------------
Upon failing, all the changes do appear to get pulled down but appear as untracked files in the but the head doesn't match the remote index.
It would seem the obvious issue is they have an authentication issue but normally if sourcetree would ask you to sign in again but it isn't this case. I've been told they had signed into Sourcetree using Google OAuth if that makes a difference.