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
Make reporting replay system deploys #3397
Make reporting replay system deploys #3397
Conversation
1eb3df7
to
e43bfdf
Compare
bors try |
tryBuild succeeded: |
e43bfdf
to
1f70dd1
Compare
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
149e581
to
331b887
Compare
casper/src/main/scala/coop/rchain/casper/util/rholang/CasperRhoRuntimeSyntax.scala
Outdated
Show resolved
Hide resolved
casper/src/test/scala/coop/rchain/casper/batch1/MultiParentCasperReportingSpec.scala
Outdated
Show resolved
Hide resolved
331b887
to
6dd5687
Compare
casper/src/main/scala/coop/rchain/casper/api/BlockReportAPI.scala
Outdated
Show resolved
Hide resolved
As we discussed on standup. Let's keep reporting API on external and internal the same with force parameter included. Reporting is protected with config flag. |
} yield SystemDeployReportResult(term.systemDeploy, r) | ||
} | ||
|
||
checkPoint <- runtime.createCheckpoint |
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.
createCheckpoint
here would store the items again which is not neccessary at all. All we need here is the proof while the history current implementation is difficult to change the storing part we would leave that into another pr.
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.
Nice refactoring!
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
bors merge |
Build succeeded: |
Overview
Make reporting replay system deploys and adds parameter
forceReplay
to trace API method to execute reporting replay even when exists in cache.Related #2981
Reporting API is now also available together with other methods on web and admin
/api/trace
route. Oldreporting/trace
is not changed.Please make sure that this PR:
Bors cheat-sheet:
bors r+
runs integration tests and merges the PR (if it's approved),bors try
runs integration tests for the PR,bors delegate+
enables non-maintainer PR authors to run the above.