-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Replace assertInvariantsBlockly invariantsCheckFrequency #4083
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #4083 +/- ##
==========================================
+ Coverage 59.98% 60% +0.01%
==========================================
Files 211 211
Lines 15109 15113 +4
==========================================
+ Hits 9063 9068 +5
+ Misses 5426 5425 -1
Partials 620 620 |
Attaching test evidence:
|
9c91f54
to
3bb31f1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concept ACK.
The thing you call "frequency" is a "period" between invariant checks - a "frequency" would be its inverse. Also the logic could be simplified a bit (see comment).
3bb31f1
to
7692234
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A minor nit on naming, but functionally LGTM.
b46ed52
to
189e3d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, @alessio can you please update the testnet
command to also set a period of idk...maybe 10?
gaiaConfig := srvconfig.DefaultConfig()
gaiaConfig.MinGasPrices = viper.GetString(server.FlagMinGasPrices)
// set the value here
I disagree @alexanderbez for 2 reasons:
|
I respectfully disagree. I don't think we should absolutely hinder the development and refinement of PRs, especially from the context of review, due to the scope of the ACs -- this is my primary beef with forcing us to have concrete ACs. I can think of a whole host of prior PRs that would end up being half-baked in nature because they simply met what would be their ACs at the time. As long as issues have a clearly stated bug or feature and the desired actionable items, that suffices in most cases. I'll be more than happy to add this feature myself -- it's a one liner (Dockerfile). EDIT/TL;DR: What I'm really trying to say is that the ACs, as they're defined (regardless of format), should be "soft" criteria. |
what about if we move this conv outside so we don't block this PR ? |
Dear @alexanderbez First and foremost, I want to thank you for raising this issue and reassure you that I am sympathetic with you. Clearly you want to deliver the best outcome possible. So do I. I am confident that you believe me. Having said that, I also believe that giving the user the option to customise Stories' Acceptance Criteria are there for a reason. They by no means represent the ultimate solutions to problems: you're absolutely right there, they're intrinsically meant to partially address issues. AC are though functional to our common goal of delivering the best possible product for our users. In my very humble opinion, even before delivering this, we should sit down and write acceptance criteria for a new issue whose ultimate goal should be to address what would be left to be done once this is PR is approved and merged.
In light of the above, supposing that there are no other technical implementation-related concerns that might prevent us of approving and merging this PR, we really should let this small piece of code in and work out our next step towards a better product. |
* Merge PR #4163: Fix v0.33.x export script to port gov data correctly * Remove TOC * Add missing changelog entry for v0.34.1 * Merge PR #4182: Cherry pick #4083 into v0.34.2 * Merge PR #4181: Cherry pick 4135 v0.34.2 * Merge PR #4183: Cherry pick 4181 into v0.34.2 * Support pagination and status query params for /staking/validators * Rename BondStatusToString to String * Cherry pick 4181 * Remove pending log * Fix CODEOWNERS
Replace gaiad's
--assert-invariants-blockly
with--inv-check-period
Closes: #4053
docs/
)sdkch add [section] [stanza] [message]
Files changed
in the github PR explorerFor Admin Use: