-
Notifications
You must be signed in to change notification settings - Fork 212
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
[Merged by Bors] - mesh/executor: extend atxsdata with coinbase to use them when applying blocks #5547
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #5547 +/- ##
=======================================
Coverage 79.7% 79.7%
=======================================
Files 267 267
Lines 26831 26828 -3
=======================================
+ Hits 21388 21395 +7
+ Misses 3924 3913 -11
- Partials 1519 1520 +1 ☔ View full report in Codecov by Sentry. |
@@ -39,7 +39,9 @@ const ( | |||
|
|||
type testMesh struct { | |||
*Mesh | |||
db sql.Executor | |||
db *sql.Database | |||
cdb *datastore.CachedDB |
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.
I think this field is unused?
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.
it is used in malfeasence.Validate, which is called in the tests, i wanted to avoid refactoring that module in the one change
bors merge |
…g blocks (#5547) related: #5192 it adds around 20MB per 1_000_000 atxs. i considered getting them from database (e.g we can do select using atx id primary key index and read coinbase), but it is likely that number of proposals continue to grow in the foreseeable future (each proposal is a separate query) so storing a bit more data is a better option.
Build failed:
|
needs rebase |
bors merge |
…g blocks (#5547) related: #5192 it adds around 20MB per 1_000_000 atxs. i considered getting them from database (e.g we can do select using atx id primary key index and read coinbase), but it is likely that number of proposals continue to grow in the foreseeable future (each proposal is a separate query) so storing a bit more data is a better option.
Build failed: |
aa0cd29
to
065c400
Compare
bors merge |
…g blocks (#5547) related: #5192 it adds around 20MB per 1_000_000 atxs. i considered getting them from database (e.g we can do select using atx id primary key index and read coinbase), but it is likely that number of proposals continue to grow in the foreseeable future (each proposal is a separate query) so storing a bit more data is a better option.
Build failed: |
bors merge |
…g blocks (#5547) related: #5192 it adds around 20MB per 1_000_000 atxs. i considered getting them from database (e.g we can do select using atx id primary key index and read coinbase), but it is likely that number of proposals continue to grow in the foreseeable future (each proposal is a separate query) so storing a bit more data is a better option.
Pull request successfully merged into develop. Build succeeded: |
related: #5192
it adds around 20MB per 1_000_000 atxs.
i considered getting them from database (e.g we can do select using atx id primary key index and read coinbase),
but it is likely that number of proposals continue to grow in the foreseeable future (each proposal is a separate query)
so storing a bit more data is a better option.