We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When building for linux-amd64 I'm getting the error:
# github.com/zk-org/zk/internal/adapter/editor note: module requires Go 1.21 go build github.com/zk-org/zk/internal/adapter/editor: /usr/local/go/pkg/tool/linux_amd64/compile: signal: segmentation fault # github.com/mattn/go-sqlite3 gcc: internal compiler error: Segmentation fault signal terminated program cc1
I'm assuming this is (solely) due to upgrading the version dependancy in go.mod for zk source.
go.mod
zk
So @zk-org/maintainers How should we handle this fix considering we're an org now and want to bother you as little as possible, Mickael?
Docker org requires a paid team plan. So one of us new maintainers should take over the images on docker hub?
Or we could make a dummy email for a 'zk-org' user and share a password?
Thoughts?
I would vote for a dummy email and shared password as it avoids this thorn if / when a maintainer also needs some time out temporarily or permanently.
The text was updated successfully, but these errors were encountered:
continue on from here: #2 (comment)
Sorry, something went wrong.
No branches or pull requests
When building for linux-amd64 I'm getting the error:
I'm assuming this is (solely) due to upgrading the version dependancy in
go.mod
forzk
source.So @zk-org/maintainers
How should we handle this fix considering we're an org now and want to bother you as little as possible, Mickael?
Docker org requires a paid team plan. So one of us new maintainers should take over the images on docker hub?
Or we could make a dummy email for a 'zk-org' user and share a password?
Thoughts?
I would vote for a dummy email and shared password as it avoids this thorn if / when a maintainer also needs some time out temporarily or permanently.
The text was updated successfully, but these errors were encountered: