Skip to content

chore(deps): bump go.etcd.io/bbolt to v1.3.9#49

Open
moralpriest wants to merge 1 commit into
DEROFDN:community-devfrom
moralpriest:chore/deps/bbolt-v1.3.9
Open

chore(deps): bump go.etcd.io/bbolt to v1.3.9#49
moralpriest wants to merge 1 commit into
DEROFDN:community-devfrom
moralpriest:chore/deps/bbolt-v1.3.9

Conversation

@moralpriest

Copy link
Copy Markdown

Summary

Vendored dependency bump (prep for eventual Go toolchain bump).

  • go.etcd.io/bbolt: v1.3.9 (go 1.17, latest go<=1.17). The underlying key-value store for deroproject/graviton (DERO storage layer).

Solo PR (per review: storage split from encoding). All go <= 1.17 — clean standalone.

Verification

  • go build ./... green.
  • go test ./...: bbolt's own suite (db/tx/cursor/bucket tests) and the graviton package both pass. The only failure is Test_Payload_TX (walletapi) — pre-existing, reproduced identically on a clean community-dev worktree.
  • derod --testnet starts, opens/closes the DB cleanly (no errors/panics in startup log).

bbolt v1.3.x is a stable line; the on-disk format is backward-compatible, so existing chain databases are unaffected.

Follow-ups

Remaining go<=1.17 vendored-dep candidates: cbor, metrics (VictoriaMetrics+histogram), env, go-colorful, pkg/profile, kcp-go, robfig/cron. (cespare/xxhash deferred as consensus-critical; tjfoc/gmsm unused; blang/semver + go.uber.org/atomic already at latest; go-logr/zapr deferred until logr v1.2.4 / PR #46 lands.)

Vendored dependency bump (prep for eventual Go toolchain bump).

- go.etcd.io/bbolt: v1.3.9 (go 1.17, latest go<=1.17). The underlying
  key-value store for deroproject/graviton (DERO storage layer).

Verification:
- go build ./... green.
- go test ./...: bbolt's own suite (db/tx/cursor/bucket) and the
  graviton package both pass. Only pre-existing failure is
  Test_Payload_TX (walletapi, reproduced on clean community-dev).
- derod --testnet starts, opens/closes the DB cleanly (no errors/panics
  in startup log; 14 CORE log lines).

bbolt v1.3.x is a stable line; on-disk format is backward-compatible,
so existing chain DBs are unaffected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant