Tony Z

did a quick search on github and found this: https://github.com/dave/jennifer. not sure if it's battle-tested though.

bors merge

will merge it first and treat https://github.com/onflow/flow-go/issues/3393 as a separate fix in future PR

bors merge

bors retry

the current EN upload call will automatically [retry](https://github.com/onflow/flow-go/blob/master/engine/execution/computation/computer/uploader/uploader.go#L66) for [5 times](https://github.com/onflow/flow-go/blob/master/cmd/execution_builder.go#L83), besides the retry feature we recently added in #2743 . So the question is whether we should retry upload...

Thanks for the suggestion. Now I have another question: how often, and when, are meter settings mutated? In this draft PR we are trying to read the state at the...

To add up: to make sure meter setting state regs are sent over to VN for verification purposes, we will still need to touch those reg per collection. > Thanks...

after [discussion](https://docs.google.com/document/d/1b0HtraCXs57o44JexkbidXj4F-iAlhPuVFj7NsCrNPc/edit?usp=sharing) we decided to use state-replay cache to do cached state reads while keeping the original reg touch records.

bors merge