Arch Linux User Repository

@tarball ahh go clean -modcache did the trick sorry about that.

Just cloned it and rebuilt under a freshly created unix user, works fine. Maybe you could try cleaning your go build & module caches?

% go clean -cache

Latest update seems to fail builld?

==> Starting build()...

gopkg.in/yaml.v3

/home/<user>/go/pkg/mod/gopkg.in/yaml.v3@v3.0.1/encode.go:81:9: undefined: yaml_emitter_emit pkg/cmd/root.go:1: running "go": exit status 1 ==> ERROR: A failure occurred in build(). Aborting... -> error making: stripe-cli-exit status 4 -> Failed to install the following packages. Manual intervention is required: stripe-cli - exit status 4

Update: go clean -modcache did the trick for me.

@Minmo: I had the same problem. It turned out to be syncthing using port 8080. You probably have a program using that port on localhost.

@Minmo: sorry, I cannot reproduce it... If it's test file problem, this problem should reported to upstream. I cannot modify upstream code :(

Build fails because some tests are missing

go test  -failfast -race -coverpkg=./... -covermode=atomic -coverprofile=coverage.txt ./... -run . -timeout=2m
?       github.com/stripe/stripe-cli/cmd/stripe [no test files]
?       github.com/stripe/stripe-cli/pkg/ansi   [no test files]
ok      github.com/stripe/stripe-cli/pkg/cmd    0.276s  coverage: 15.8% of statements in ./...
?       github.com/stripe/stripe-cli/pkg/cmd/logs       [no test files]
ok      github.com/stripe/stripe-cli/pkg/cmd/resource   0.240s  coverage: 17.1% of statements in ./...
?       github.com/stripe/stripe-cli/pkg/cmd/samples    [no test files]
ok      github.com/stripe/stripe-cli/pkg/config 0.230s  coverage: 15.8% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/fixtures       0.242s  coverage: 20.3% of statements in ./...
?       github.com/stripe/stripe-cli/pkg/git    [no test files]
ok      github.com/stripe/stripe-cli/pkg/login  0.303s  coverage: 18.7% of statements in ./...
?       github.com/stripe/stripe-cli/pkg/logout [no test files]
ok      github.com/stripe/stripe-cli/pkg/logtailing     0.215s  coverage: 14.8% of statements in ./...
?       github.com/stripe/stripe-cli/pkg/open   [no test files]
2021/10/12 11:52:20 server startup failed - Listen(): listen tcp 127.0.0.1:8080: bind: address already in use
FAIL    github.com/stripe/stripe-cli/pkg/playback       0.194s
ok      github.com/stripe/stripe-cli/pkg/proxy  0.209s  coverage: 16.7% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/requests       0.207s  coverage: 17.0% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/rpcservice     0.363s  coverage: 31.3% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/samples        0.187s  coverage: 15.8% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/spec   2.700s  coverage: 15.0% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/status 0.229s  coverage: 15.1% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/stripe 0.255s  coverage: 16.0% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/stripeauth     0.221s  coverage: 15.9% of statements in ./...
?       github.com/stripe/stripe-cli/pkg/terminal       [no test files]
ok      github.com/stripe/stripe-cli/pkg/terminal/p400  0.207s  coverage: 15.0% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/useragent      0.207s  coverage: 14.7% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/validators     0.191s  coverage: 15.4% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/version        0.189s  coverage: 14.7% of statements in ./...
ok      github.com/stripe/stripe-cli/pkg/websocket      0.205s  coverage: 16.9% of statements in ./...
?       github.com/stripe/stripe-cli/rpc        [no test files]
FAIL
make: *** [Makefile:23: test] Error 1

Hi SamWhited, currently I don't use this package and I usually just change version number when updated, so I'd like you to fix (and update) this time if you don't mind. Thanks!

Hi ny-a; thanks for following up (and for adding me as a co-maintainer). I'd be happy to help maintain the patch until Stripe fixes the problem if you want, but I don't want to step on any toes either. Let me know how I can help, and thanks again.

SamWhited, thanks for your patch. But I can't maintain patch for long time, so it's preferable to be merged by upstream, you know. Maybe closing PR and opening issue is a way to have some progress.