-
Notifications
You must be signed in to change notification settings - Fork 71
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
Hardened JavaScript interferes with Node.js 14 Error construction #868
Comments
Although #867 fixes the issue revealed here, it won't actually change this specific occurrence. The problematic Node code might override the |
@kriskowal Can you please put an estimate on this? |
@erights I’m not clear on whether or what the next steps for this issue would be. Is there fix we could stomach that would address this issue at all overrideTaming settings? |
Well, we could trivially copy this Have we told Node about this? Have we filed an issue? Is it still a problem on Node 16? |
@kriskowal This does not have an area label that is covered by our weekly tech / planning meetings. Can you assign the proper label? We cover: agd, agoric-cosmos, amm, core economy, cosmic-swingset, endo, getrun, governance, installation-bundling, metering, run-protocol, staking, swingset, swingset-runner, token economy, wallet, zoe contract, |
We no longer support Node.js 14. |
@warner reports:
The relevant code in Node.js 14.17.4 is:
And the culprit is the property override hazard, upon assigning to
name
of an instance descended from a frozen error constructor.The text was updated successfully, but these errors were encountered: