Skip to content
This repository has been archived by the owner on Feb 9, 2021. It is now read-only.

Spec-versus-impl sanity check: make sure all spec errors are thrown by implementation #709

Open
edsko opened this issue Feb 5, 2020 · 1 comment
Labels
byron Required for a Byron mainnet: replace the old core nodes with cardano-node. consensus Tickets that the fine folks over at ouroboros-consensus want to keep track of priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn

Comments

@edsko
Copy link
Contributor

edsko commented Feb 5, 2020

We should make sure that (the translation of) all errors that can be thrown by the specification can also be thrown by the implementation.

We should also remove unused errors (#670), but note that some of these errors might currently be thrown by the integration of the Byron ledger within consensus, rather than by code in the Byron ledger. If that is true, that should be changed as part of #708.

@edsko edsko added byron Required for a Byron mainnet: replace the old core nodes with cardano-node. consensus Tickets that the fine folks over at ouroboros-consensus want to keep track of priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn labels Feb 5, 2020
@edsko edsko mentioned this issue Feb 5, 2020
@edsko
Copy link
Contributor Author

edsko commented Feb 5, 2020

Related: #616.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
byron Required for a Byron mainnet: replace the old core nodes with cardano-node. consensus Tickets that the fine folks over at ouroboros-consensus want to keep track of priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn
Projects
None yet
Development

No branches or pull requests

1 participant