Runtime error when automating with CLI

That's very good feedback. I agree with you that I'd expect that to use the latest version.

I'll loop that back to our team. Thanks for sharing this! 🙌

@Joris_1P a Side note:
Your guide here:https://developer.1password.com/docs/cli/get-started/
Has Invoke-WebRequest ... v2.4.1 .... v2.4.1.zip.

I was working with that version for a while because it didn't occur to me your documentation was that far out of date. Maybe you could make a link to "latest" like you do with the Windows app?

Thanks for confirming. That's great to hear!

Hi @Joris_1P

I've ran 100 calls this morning after updating to V2.11.0, and i dont get the error anymore. Thanks for the update. :)

Hey folks! We have just released v2.11.0 of 1Password CLI, which should address this issue. See https://developer.1password.com/docs/cli/reference/update/ for instructions on how to update.

Let us know if you are still having issues with v2.11.0 or later.

hi folks,

im new to 1password and have same issue with CLI 2.10.0 in my Powershell Script:
doing:
$chatid = "$(op read op://Private/TelegramBot/chat_id)"
and sometimes it gives me a looooong error message.

-- snip --
runtime: setevent failed; errno=6
fatal error: runtime.semawakeup

runtime stack:
runtime.throw({0x142185e?, 0x9f5e65?})
/usr/local/go/src/runtime/panic.go:1047 +0x65 fp=0x75b7bffc28 sp=0x75b7bffbf8 pc=0x9f93c5
runtime.semawakeup.func1()
/usr/local/go/src/runtime/os_windows.go:874 +0x70 fp=0x75b7bffc50 sp=0x75b7bffc28 pc=0x9f52d0
runtime.semawakeup(0x1b40dd61d8b4?)
/usr/local/go/src/runtime/os_windows.go:872 +0x56 fp=0x75b7bffc78 sp=0x75b7bffc50 pc=0x9f5336
runtime.notewakeup(0x75b7bffcb0?)
/usr/local/go/src/runtime/lock_sema.go:161 +0x4e fp=0x75b7bffc98 sp=0x75b7bffc78 pc=0x9cc60e
runtime.startm(0x0, 0x1)
/usr/local/go/src/runtime/proc.go:2344 +0x1e8 fp=0x75b7bffce0 sp=0x75b7bffc98 pc=0x9ffd48
runtime.wakep()
/usr/local/go/src/runtime/proc.go:2430 +0x5a fp=0x75b7bffd00 sp=0x75b7bffce0 pc=0xa0019a
runtime.resetspinning()
/usr/local/go/src/runtime/proc.go:3110 +0x45 fp=0x75b7bffd20 sp=0x75b7bffd00 pc=0xa01b65
runtime.schedule()
/usr/local/go/src/runtime/proc.go:3220 +0xe5 fp=0x75b7bffd58 sp=0x75b7bffd20 pc=0xa01fa5
runtime.park_m(0xc0005049c0?)
/usr/local/go/src/runtime/proc.go:3363 +0x14d fp=0x75b7bffd88 sp=0x75b7bffd58 pc=0xa024ad
runtime.mcall()
/usr/local/go/src/runtime/asm_amd64.s:448 +0x4a fp=0x75b7bffd98 sp=0x75b7bffd88 pc=0xa26a0a

goroutine 1 [runnable]:
math/big.nat.divBasic({0xc00042f4a0, 0x11, 0x15?}, {0xc000328000, 0x21, 0x24}, {0xc000034900, 0x10, 0x44})
/usr/local/go/src/math/big/natdiv.go:621 +0x718 fp=0xc000454e30 sp=0xc000454e28 pc=0xbb26b8
math/big.nat.divLarge({0x0, 0x0?, 0x0}, {0xc000328000, 0x10?, 0x24}, {0xc000328000, 0x10?, 0x24}, {0xc00042ec60, ...})

/usr/local/go/src/math/big/natdiv.go:603 +0x3a6 fp=0xc000454f08 sp=0xc000454e30 pc=0xbb1dc6
math/big.nat.div({0x0?, 0x0, 0x0}, {0xc000328000?, 0x20, 0x24}, {0xc000328000?, 0x20, 0x24}, {0xc00042ec60, ...})
/usr/local/go/src/math/big/natdiv.go:525 +0x328 fp=0xc000454fc8 sp=0xc000454f08 pc=0xbb1408
math/big.(*Int).QuoRem(0xc0004550b0, 0xc00025f1e0, 0xc00025f100, 0xc00025f1e0)
/usr/local/go/src/math/big/int.go:237 +0x9c fp=0xc000455050 sp=0xc000454fc8 pc=0xb9fffc
math/big.(*Int).Mod(0xc00025f1e0, 0xc00025f1e0?, 0xc00025f1a0?)
/usr/local/go/src/math/big/int.go:268 +0x205 fp=0xc000455100 sp=0xc000455050 pc=0xba03a5
crypto/rsa.decrypt({0x1593c80?, 0x1c0f100}, 0xc00025b200, 0xc00029f338)
/usr/local/go/src/crypto/rsa/rsa.go:599 +0x56c fp=0xc000455270 sp=0xc000455100 pc=0xc1b54c
crypto/rsa.DecryptOAEP({0x159dc00, 0xc000450620}, {0x1593c80, 0x1c0f100}, 0xc00025b200, {0xc000102600, 0x100, 0x100}, {0x0,
0x0, ...})
/usr/local/go/src/crypto/rsa/rsa.go:676 +0x211 fp=0xc000455368 sp=0xc000455270 pc=0xc1bb31
go.1password.io/core-security/crypto.(*RSAPrivateKey).DecryptV1(0xc0001afe60, 0xc000261200)
/builds/dev/b5/op/vendor/go.1password.io/core-security/crypto/rsa.go:162 +0x345 fp=0xc000455418 sp=0xc000455368 pc=0xc889a5
go.1password.io/core-security/crypto.(*KeysetV1).DecryptV1(0x5?, 0x80?)
/builds/dev/b5/op/vendor/go.1password.io/core-security/crypto/keyset_v1.go:70 +0xc7 fp=0xc000455468 sp=0xc000455418
pc=0xc85ac7
go.1password.io/core-security/crypto.(*EncryptedKeysetV1).DecryptV1(0xc000136ee0, {0x15996d0?, 0xc00032d020?})
/builds/dev/b5/op/vendor/go.1password.io/core-security/crypto/encryptedkeyset_v1.go:74 +0x54 fp=0xc000455520 sp=0xc000455468 pc=0xc83894
go.1password.io/core-security/crypto.(*EncryptedKeysetV1).Decrypt(0x12e8da0?, {0x211746dd7d8?, 0xc00032d020})
/builds/dev/b5/op/vendor/go.1password.io/core-security/crypto/encryptedkeyset_v1.go:64 +0x45 fp=0xc000455550 sp=0xc000455520 pc=0xc837e5

-- snap --

Hi @Pelitkm:

Thanks for letting us know about this. We're actively investigating this, so please keep an eye out for updates.

Jack

ref: dev/b5/op#2611

I encountered the error again after updating to 2.9.1. I then tried to stress test it in a CMD. And i encountered this error, first time i get it:
"[ERROR] 2022/12/13 10:45:31 failed to keysetsAPI.GetAllEncrypted: Get "https://:OURTENANT:.1password.eu/api/v2/account/keysets?__t=1670924731.314": read tcp :MY_IP:52252->52.59.131.85:443: wsarecv: An established connection was aborted by the software in your host machine."

This made me think that maybe the "connect with 1password CLI" setting in the windows app was at fault. And after disabling the feature I've ran 100 calls without the Runtime error. And it usually failed 30% of the time. So I think its safe to assume the Windows client is causing the bug, with the integration to the CLI.

It looks like it might be a bug in CLI version 2.7.3. How i even got that version i dont know, as the powershell script i ran says:
"Invoke-WebRequest -Uri "https://cache.agilebits.com/dist/1P/op2/pkg/v2.4.1/op_windows_$($opArch)_v2.4.1.zip" -OutFile op.zip".
That version works for a colleague. I've now downloaded version 2.9.1 and i cant seem to get it to fail. However i cant seem to locate version 2.7.3 so i can purge it.

Hi,

I've done some more testing, and the same error happens if I just run the single command in a CMD multiple times. So it doesn't have anything to do with my script, but an error in the CLI/communication with the cloud. I've made sure there is no HTTPS inspection through our firewall towards 1password, so it isn't an issue here.