Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] - `TracerConsistencyWarnings`: duplicate namespace `ChainDB.PerasVoteDbEvent.AddVote` / `GarbageCollected`

Open
  • Is something wrong?
#6,714 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
haskell
Domain
distributed-systems

Research direction

Build cardano-node at revision 8ff994d2fc5ae4d44a6c7240ad7ac854c2ab2cd4 on the koslambrou/prepare-11.2 branch and reproduce the startup warning on a Conway testnet with protocol version 11 and ExperimentalProtocolsEnabled enabled. Trace the registration paths for ChainDB.PerasVoteDbEvent.AddVote and GarbageCollected, including their era gating and TraceOptions handling. Done means each namespace is registered once and startup emits no TracerConsistencyWarnings when Peras is off.

Written by the indexing model from the issue text.

Description

needs triage

Internal/External
Internal

Area
Other Any other topic (Delegation, Ranking, ...).

Summary
On the koslambrou/prepare-11.2 integration branch, cardano-node logs a Reflection.TracerConsistencyWarnings trace on every start. It reports two duplicate namespaces in the ChainDB.PerasVoteDbEvent tracer:

{"at":"2026-10-01T15:42:20.442630005Z","ns":"Reflection.TracerConsistencyWarnings","data":{"errors":"["System namespace error: Duplicate namespace ChainDB.PerasVoteDbEvent.AddVote","System namespace error: Duplicate namespace ChainDB.PerasVoteDbEvent.GarbageCollected"]","kind":"TracerConsistencyWarnings"},"sev":"Warning","thread":"5","host":"c27f27bfdd8b"}

So the namespaces ChainDB.PerasVoteDbEvent.AddVote and ChainDB.PerasVoteDbEvent.GarbageCollected are each registered more than once. As a result, they can't be configured unambiguously through TraceOptions.

This may be related to Peras integration. Peras is being integrated for 11.2, but all Peras features should be off in the Conway and Dijkstra eras. The Peras vote DB tracers being registered, and registered twice, on a Conway network could be another symptom of Peras wiring that isn't properly gated.

Steps to reproduce

  1. Build cardano-node from koslambrou/prepare-11.2.
  2. Start a local testnet, Conway era, protocol version 11, ExperimentalProtocolsEnabled: true.
  3. Look at the node's stdout right after startup.

The warning appears on every node and on every start or restart. The node configuration has no TraceOptions entries for any Peras namespace, so it doesn't depend on user configuration.

Expected behavior

  • Every trace namespace is registered once, and startup emits no TracerConsistencyWarnings.
  • With Peras off in Conway and Dijkstra, Peras-specific tracers shouldn't cause warnings on a Conway network.

System info (please complete the following information):

  • OS Name: Ubuntu
  • Branch koslambrou/prepare-11.2, git rev 8ff994d2fc5ae4d44a6c7240ad7ac854c2ab2cd4. The node still reports its version as cardano-node 11.1.1.
  • cardano-cli 11.2.3.1
  • linux-x86_64, ghc-9.6.7
Dominant language
Haskell
Stars
3.2k
Forks
760
Avg merge
2d 7h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/cardano-node

All issues in IntersectMBO/cardano-node

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.