mirror of
https://github.com/hanzoai/s3.git
synced 2026-10-30 14:59:09 +00:00
zeekayandHanzo Dev
b6694c9af7
Eight places assigned a protobuf message by value. That copies protoimpl.MessageState with the fields — a mutex and the lazy-init bookkeeping the proto runtime owns — which is why vet refused the whole repository, and why a hand-rolled deep clone of a heartbeat was copying each nested message the same way. proto.Clone does all of it; proto.Reset with proto.Merge is the in-place overwrite, where one was overwriting through a pointer. One field held a message by value to mean two things, so its companion bool went with it: a nil pointer already says there is no last good status. The repository passes vet for the first time, and four of its seven modules build on Go 1.27. The other three ask for at their own current directive, before any change here, so they are left as they are. Co-authored-by: Hanzo Dev <[email protected]>
18 lines
926 B
AMPL
18 lines
926 B
AMPL
// Drop-in module for github.com/tyler-smith/go-bip39, whose upstream GitHub
|
|
// repository was deleted (fetch fails under GOPROXY=direct). It re-exports the
|
|
// luxfi fork (github.com/luxfi/go-bip39, API-compatible) under the original
|
|
// module path so the lone transitive consumer (rclone's internxt backend, via
|
|
// github.com/internxt/rclone-adapter) keeps building without depending on the
|
|
// dead upstream. A plain `replace tyler-smith/go-bip39 => luxfi/go-bip39` is not
|
|
// possible: the luxfi fork renamed its module path and self-imports
|
|
// github.com/luxfi/go-bip39/wordlists, so one module version would have to serve
|
|
// two module paths ("used for two different module paths"). This thin shim is a
|
|
// distinct module under the original path, so `go mod tidy` resolves cleanly.
|
|
module github.com/tyler-smith/go-bip39
|
|
|
|
go 1.27.1
|
|
|
|
require github.com/luxfi/go-bip39 v1.1.2
|
|
|
|
require golang.org/x/crypto v0.40.0 // indirect
|