Skip to content

chore(deps): bump go.uber.org/zap to v1.21.0 and multierr to v1.8.0#47

Open
moralpriest wants to merge 1 commit into
DEROFDN:community-devfrom
moralpriest:chore/deps/logging-stack-v1.2.4-v1.21.0
Open

chore(deps): bump go.uber.org/zap to v1.21.0 and multierr to v1.8.0#47
moralpriest wants to merge 1 commit into
DEROFDN:community-devfrom
moralpriest:chore/deps/logging-stack-v1.2.4-v1.21.0

Conversation

@moralpriest

Copy link
Copy Markdown

Summary

Vendored dependency bumps (prep for eventual Go toolchain bump). Bumps the logging backend stack:

  • go.uber.org/zap: v1.21.0 (go 1.13; was v1.13-era). The concrete structured-logging backend behind the logr/zapr adapter (globals/globals.go:182 zapr.NewLogger(zcore)).
  • go.uber.org/multierr: v1.8.0 (go 1.14, latest go<=1.17). zap dependency.
  • go.uber.org/atomic: intentionally NOT bumped — already at v1.9.0 (latest go<=1.17); verified byte-identical to current vendored copy (no-op).
  • go-logr/zapr: deferred to a follow-up PR. zapr v1.2.4 requires logr v1.2.4 (PR chore(deps): bump go-logr/logr to v1.2.4 #46), which is not yet merged into community-dev. This PR is self-contained and logr-independent.

Why this is safe

  • Both targets are go <= 1.17 (our directive) — clean standalone PRs, no go-directive bump.
  • zap/multierr are the logging backend only; they do not affect consensus, PoW, or SC execution.
  • atomated at latest go<=1.17; no new transitive requires introduced.

Verification

  • go build ./... — green (exit 0).
  • go test ./globals/... — pass (exercises globals.go:182 zapr.NewLogger wiring + logger recovery).
  • go vet ./... — clean (only pre-existing unkeyed fields warnings in dvm/simulator_test.go, unrelated).
  • Smoke test: derod --testnet starts and logs via the zap backend (CORE/MEMPOOL/REGPOOL emit correctly).
  • run_integration_test.sh: the single failure (lottery_within_block_1panic_1success_test) is pre-existing — reproduced identically on a clean community-dev worktree. SC lottery logic, unrelated to a logging-backend bump.

Follow-ups

  • zapr v1.2.4 once logr v1.2.4 (PR chore(deps): bump go-logr/logr to v1.2.4 #46) lands in community-dev.
  • Remaining go<=1.17 vendored-dep candidates: terminal family (mattn/*, fatih/color), bbolt, cbor, metrics (VictoriaMetrics+histogram), env, go-colorful, pkg/profile, kcp-go, robfig/cron. (cespare/xxhash deferred as consensus-critical; tjfoc/gmsm unused; blang/semver already at latest.)

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

- go.uber.org/zap: v1.21.0 (go 1.13, was v1.13-era). Concrete logging
  backend behind the logr/zapr adapter.
- go.uber.org/multierr: v1.8.0 (go 1.14, latest go<=1.17). zap dependency.
- go.uber.org/atomic intentionally NOT bumped: already at v1.9.0 (latest
  go<=1.17) — verified byte-identical (no-op).

Verification:
- go build ./... green
- go test ./globals/... pass (exercises globals.go:182 zapr.NewLogger wiring)
- go vet ./... clean (only pre-existing unkeyed-field warnings in dvm tests)
- derod --testnet starts and logs via zap backend (CORE/MEMPOOL/REGPOOL)
- run_integration_test.sh: only pre-existing failure
  (lottery_within_block_1panic_1success_test) reproduced identically on clean
  community-dev worktree — not a regression.

Note: go-logr/zapr v1.2.4 deferred to a follow-up PR because it requires
logr v1.2.4 (PR DEROFDN#46), which is not yet merged into community-dev.
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