op signin error
Hello,
I am attempting to use the 1password CLI for the first time on my laptop, but after I attempt to sign in and provide my domain, email, and secret key; the system encounters the error below:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x40234c]
goroutine 1 [running]:
runtime/internal/atomic.Xadd64(0x115b62bc, 0x1, 0x0, 0x1, 0x115a6150)
/usr/local/go/src/runtime/internal/atomic/asm_386.s:105 +0xc
go.1password.io/op/b5/model.(Session).NextRequestID(0x115b6280, 0x115a6150, 0x1)
/go/src/go.1password.io/op/b5/model/session.go:52 +0x36
go.1password.io/op/b5/api/request.Init(0x115b6280, 0x1, 0x1140c3f0, 0x2e, 0x7b7400, 0x114183c0, 0x2e, 0x0, 0x0)
/go/src/go.1password.io/op/b5/api/request/request.go:213 +0xf8
go.1password.io/op/b5/api/auth.SRPVerify(0x114525c0, 0x1b, 0x11548100, 0x1140a4e0, 0x20, 0x20, 0x11548040, 0x0, 0x0, 0x2)
/go/src/go.1password.io/op/b5/api/auth/auth.go:112 +0x28f
go.1password.io/op/b5/api.SigninWithCredentials(0x894da0, 0x11476210, 0x114529a0, 0x1a, 0x7f2573, 0xd, 0x7ee5eb, 0x7, 0x114529e0, 0xf, ...)
/go/src/go.1password.io/op/b5/api/signin.go:144 +0x504
go.1password.io/op/command.(SigninCommand).Run(0x114447e8, 0x11447a70, 0x2, 0x2, 0x1144c410)
/go/src/go.1password.io/op/command/signin.go:62 +0x153
go.1password.io/op/vendor/github.com/mitchellh/cli.(*CLI).Run(0x114a60a0, 0x12, 0x0, 0x11426000)
/go/src/go.1password.io/op/vendor/github.com/mitchellh/cli/cli.go:255 +0x1ce
main.run(0x0, 0x0, 0x0)
/go/src/go.1password.io/op/main.go:47 +0xa2
main.main()
/go/src/go.1password.io/op/main.go:29 +0x1a
Did I do something incorrectly or is this an issue with the current version of the CLI?
1Password Version: 0.6.1
Extension Version: Not Provided
OS Version: Windows 10
Sync Type: Not Provided
Comments
-
@pendletond We've seen a similar error on ARM architectures, am I correct in reading that you're running the 32-bit Windows version of op ?
0 -
@Pendleton - might be related to the issue I reported: https://discussions.agilebits.com/discussion/106581/op-signin-panic#latest
But, as @cohix said, I am running into the issue on ARM (raspberry pi).
Having said that, I tested op cli v0.5.7 and it seems to work for me. Can you try that version on Windows?
0 -
@cohix, I am running the 32 bit windows version
@peterbenjamin I will try downloading that version to see if it works for me.
0 -
@pendletond Since you're running Windows 10, I'm willing to bet your machine is 64-bit, so I would suggest trying the amd64 build for Windows of 0.6.1: https://cache.agilebits.com/dist/1P/op/pkg/v0.6.1/op_windows_amd64_v0.6.1.zip
Give that a try and let me know how it goes.
0 -
@cohix, that worked. I was able to log in with PowerShell on the 64 bit version. I hadn't even considered that being the issue. Thanks for the help.
0 -
@pendletond Great!
0 -
For everyone in this thread: version 0.6.2 has been released with a fix for the panic on 32-bit and ARM systems!
0
