IntersectMBO / IntersectMBO/ouroboros-consensus

Improve TraceNoLedgerView Haddock

Open
#1,849 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
67
Forks
43
Avg merge
5d 13h
Merged PRs (30d)
43

Description

It talks more about why we forecast in the forging loop instead of ticking.

But instead, the way more useful information about this message is what it implies: _something has gone wrong_ such that the node's chain is not growing anywhere nearly dense enough.

Contributor guide

Open the contributing guide

Research direction

Locate the Haddock documentation for TraceNoLedgerView and read the current explanation. Revise it to explain that the message indicates something has gone wrong because the node's chain is not growing densely enough; done means the documentation emphasizes this implication rather than forecasting in the forging loop.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.