Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed the 'All Tx are valid on traces of length 150' intermittent bug #4050

Merged
merged 1 commit into from
Feb 7, 2024

Conversation

TimSheard
Copy link
Contributor

@TimSheard TimSheard commented Feb 5, 2024

Fixed the 'All Tx are valid on traces of length 150' bug.
This was occasionally triggered at the Epoch boundary when a ParameterChange Proposal was passed,
and the PParamUpdate made random (stupid) changes to fields that made the Tx in the trace no longer valid.
Prime candidates were PParam fields that affected the computation of the fee, legal Tx sizes, and min txout values, etc.
Added function 'reasonable' to ensure bad PParamUpdates are not used. Allows users to adjust PParamUpdates in Proposals
Added EraClass -- Everything you need to build Era polymorphic Tx, all in one place

I ran this test 1000's of times without a failure while I ate dinner. I hope we have fixed it for good.
Fixes #4057 addressing the '/listSumRangeUpper.Int8.prop_sound/' bug, because it made the tests fail.

Description

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
  • Code is formatted with fourmolu (use scripts/fourmolize.sh)
  • Cabal files are formatted (use scripts/cabal-format.sh)
  • hie.yaml has been updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

@TimSheard TimSheard requested a review from lehins February 5, 2024 22:59
@TimSheard TimSheard force-pushed the ts-fix-allvalidsignals branch 2 times, most recently from 8d6cfad to d201101 Compare February 6, 2024 19:49
Copy link
Collaborator

@lehins lehins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thank you for fixing the test.

FYI, there is a conflict

@TimSheard TimSheard force-pushed the ts-fix-allvalidsignals branch from d201101 to b338230 Compare February 6, 2024 23:22
@lehins lehins enabled auto-merge February 6, 2024 23:47
…l in one place

Added 'reasonable' to ensure bad PParamUpdates are not used.
Fixed the 'All Tx are valid on traces of length 150' bug
Fixed the 'listSumRangeUpper.Int8.prop_sound' bug
@TimSheard TimSheard force-pushed the ts-fix-allvalidsignals branch from b338230 to b01c116 Compare February 7, 2024 02:44
@lehins lehins merged commit b547c77 into master Feb 7, 2024
11 of 18 checks passed
@neilmayhew neilmayhew deleted the ts-fix-allvalidsignals branch March 8, 2024 21:07
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.

Test failure on CI in the new constraint-generator package
2 participants