Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#6,714 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
haskell
Ambito
distributed-systems

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Haskell
Stelle
3.2k
Fork
760
Merge medio
2g 7h
PR unite (30g)
21

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di IntersectMBO/cardano-node

Tutte le issue di IntersectMBO/cardano-node

Issue simili

Altre issue su Haskell

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.