-
Notifications
You must be signed in to change notification settings - Fork 456
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
fix: do not always overwrite global.performance #2922
fix: do not always overwrite global.performance #2922
Conversation
a2a8a84
to
43a7212
Compare
I forked the repository to run all the unit tests |
e093d2b
to
43a7212
Compare
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.
Thank you for the contribution!!
As mentioned in the header of this file (wasm_bridge_exec), we tend to follow Golang's wasm_exec_node
. Can you update the PR to match that (specifically this)?
43a7212
to
bf4d57b
Compare
@mutahhir updated and adjusted the commit message |
@mutahhir with the changes to crypto unit tests fail, i will revert the changes for crypto
|
new node version already have a performance global, see https://nodejs.org/api/globals.html#performance it contains many methods, see https://nodejs.org/api/perf_hooks.html when always overwriting it, other modules like `undici` which use the performance object won't work any more. in general using the performance object becomes unusable as soon as the `@cdktf/hcl2json` package is required. discussion/bug: renovatebot/renovate#22615 this PR adjusts the checked in sourcefile to the latest upstream version: https://github.com/golang/go/blob/ee46f0b5084461978432aa20df003ac52500b0f0/misc/wasm/wasm_exec_node.js#L12-L17
bf4d57b
to
0120aef
Compare
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! Thank you! 🏅
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
new node version already have a performance global, see https://nodejs.org/api/globals.html#performance
it contains many methods, see https://nodejs.org/api/perf_hooks.html
when always overwriting it, other modules like
undici
which use the performance object won't work any more. in genera using the performance object become unusable as soon as the@cdktf/hcl2json
package is required.discussion/bug: renovatebot/renovate#22615
Related issue
Fixes #
Description
In plain English, describe your approach to addressing the issue linked above. For example, if you made a particular design decision, let us know why you chose this path instead of another solution.
Checklist