Biometrics Requested for Each Repo in VS Code

Gang,

I've been in love with 1P8 up until this release. This one is annoying. Really annoying. Since 80700041 hit my 2 Macs, every time I launch VS Code, and it goes to look at GitHub repos to see if things are up to date, it wants me to place my finger on the sensor for every.single.repo in the workspace I've got loaded. Yes, I counted. 13 repos loaded? 13 times. It's awful. I even tried tricks like launching vscode from inside an iTerm session that already had an authenticated agent session, and it still did it.

Build 28 definitely did not do this. 41 is doing this on both M1 and Intel. Please, make it stop. ;) Thanks for all the great code, folks.

And for the record, my .zshrc concludes with.....


export SSH_AUTH_SOCK=~/.1password/agent.sock


which is a symlink to....


~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock


1Password Version: 8.7.0 b41
Extension Version: 2.3.2
OS Version: macOS 12.3.1

I think https://1password.community/discussion/128607/biometrics-requested-for-each-repo-in-vs-code#latest reports the same issue, @jcostom .

Hey! Looks like the same issue indeed. Good to see I'm not losing my marbles. Well, at least I'm not the only one seeing this at least. Perhaps the jury's still out on the other thing. ;) Thanks @MrC .

Confirmed. Same issue here, same combo of bits. Seeing it on both M1 and Intel Macs.

Hey all - problem still exists in build 80700049.

Hey folks 👋 We are aware of this and our engineering team is working on a fix! We'll post here when we have a further update! Thank you for reporting the behavior!

The same issue applies to running an ansible playbook on multiple hosts, which all share the same SSH key.

The latest update has a note about SSH agent in its release notes: "The SSH Agent no longer prompts you to unlock twice." I just wanted to mention that this item is not a fix for what I reported, and I hope the engineers are aware of that.

@alexclst Yes, that is indeed a separate issue. We're working on a fix for that as well, stay tuned!

Thanks for the update @floris_1P. I was hopeful that 80700090 was going to be a winner, but alas, not to be. My finger's still bobbing up and down every time I open up vscode...