New VM v5.3.2 Release#1199
Conversation
…, updated upstream dependencies
|
Very little time today, so I would just publish on npm once approved and do all the rest tomorrow morning. |
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
|
||
| ## 5.3.2 - 2021-04-12 | ||
|
|
||
| This is a hot-fix performance release, removing the `debug` functionality from PR [#1080](https://github.com/ethereumjs/ethereumjs-monorepo/pull/1080) and follow-up PRs. While highly useful for debugging, this feature side-introduced a siginficant reduction in VM performance which went along unnoticed. For now we will remove since upstream dependencies are awaiting a new release before the `Belin` HF happening. We will try to re-introduce in a performance friendly manner in some subsequent release (we cannot promise on that though). |
There was a problem hiding this comment.
| This is a hot-fix performance release, removing the `debug` functionality from PR [#1080](https://github.com/ethereumjs/ethereumjs-monorepo/pull/1080) and follow-up PRs. While highly useful for debugging, this feature side-introduced a siginficant reduction in VM performance which went along unnoticed. For now we will remove since upstream dependencies are awaiting a new release before the `Belin` HF happening. We will try to re-introduce in a performance friendly manner in some subsequent release (we cannot promise on that though). | |
| This is a hot-fix performance release, removing the `debug` functionality from PR [#1080](https://github.com/ethereumjs/ethereumjs-monorepo/pull/1080) and follow-up PRs. While highly useful for debugging, this feature side-introduced a siginficant reduction in VM performance which went along unnoticed. For now we will remove since upstream dependencies are awaiting a new release before the `Belin` HF happening. We will try to re-introduce in a performance friendly manner in some subsequent release (we cannot promise on that though). The `step` event output is now also changed, with some elements not available anymore (they can be calculated on demand, though). |
There was a problem hiding this comment.
Step event also changed.
There was a problem hiding this comment.
Which ones? That's not intended.
There was a problem hiding this comment.
Just checked this again, and this is not the case. I didn't modify the code that creates eventObj, the object is not modified later, and is the only thing passed to the event listeners.
|
@jochem-brouwer sorry, don't have time to wait for CI another round, so will merge as-is. Have published on npm. |
No description provided.