Revert "Properly handle execution time<->energy conversion in v8 host (#4884)"#4927
Merged
Conversation
cloutiertyler
approved these changes
May 1, 2026
1 task
Contributor
Author
|
Just closing this for now, @coolreader18 says they have a better fix for this. |
joshua-spacetime
approved these changes
May 28, 2026
Contributor
joshua-spacetime
left a comment
joshua-spacetime
left a comment
There was a problem hiding this comment.
Unless @coolreader18 has strong objections, I would say let's merge this now in order to land the fix in master. And we can merge #4930 as a follow up.
Contributor
|
I'm going to merge this since we already know it fixes energy usage. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
This reverts commit 458eac8.
This rolls back a pricing change that we made to V8 (TypeScript) based modules. This will be applied as a hotfix to 2.2.0.
API and ABI breaking changes
None
Expected complexity level and risk
1 - Just a pricing change.
Testing