We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Node.js v20.1.0.
Linux dev 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
deps/v8/src/objects/value-serializer.cc WriteJSPrimitiveWrapper
var fo = new Boolean(false) undefined fo["#reason"] = "no-reponse-from-remote" 'no-reponse-from-remote' fo [Boolean: false] { '#reason': 'no-reponse-from-remote' } v8.serialize(fo) <Buffer ff 0d 78> v8.deserialize(v8.serialize(fo)) [Boolean: false] var not_my_false = v8.deserialize(v8.serialize(fo)) undefined not_my_false["#reason"] var also_not_my_false = structuredClone(fo) also_not_my_false [Boolean: false] also_not_my_false["#reason"]
always
Although PrimitiveWrapObject Is rarely used, But I think it should keep the extra info when serialized.
our Application use this Boolean(false) to carry "reason-info", and serialized it to a log-server.
extra info losted when deser(ser)
No response
The text was updated successfully, but these errors were encountered:
I think this issue should be reported at the v8 project
Sorry, something went wrong.
we call v8 WriteValue directly. I recommend opening a feature request here: https://bugs.chromium.org/p/v8/issues/list?q=ValueSerializer&can=1
WriteValue
got it. thinks
No branches or pull requests
Version
Node.js v20.1.0.
Platform
Linux dev 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
deps/v8/src/objects/value-serializer.cc WriteJSPrimitiveWrapper
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
Although PrimitiveWrapObject Is rarely used, But I think it should keep the extra info when serialized.
our Application use this Boolean(false) to carry "reason-info", and serialized it to a log-server.
What do you see instead?
extra info losted when deser(ser)
Additional information
No response
The text was updated successfully, but these errors were encountered: