You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've come across an inconsistency in how the byte size of JSON assertions is calculated in the Python and ot-node/dkg.js. This discrepancy has led to an error in verification of the Knowledge Asset (KA) size on the node when trying to create a KA with special characters through the dkg.py.
Details
In the Python version, when encoding a specific character (e.g., \u2022) within a JSON string, I noticed that the resulting byte size of the JSON is calculated as 22. Here's an example code snippet for illustration:
The expected behavior would be a consistent byte size calculation for JSON assertions across both the Python and NodeJS implementations (and all other).
The text was updated successfully, but these errors were encountered:
Overview
We've come across an inconsistency in how the byte size of JSON assertions is calculated in the Python and ot-node/dkg.js. This discrepancy has led to an error in verification of the Knowledge Asset (KA) size on the node when trying to create a KA with special characters through the dkg.py.
Details
In the Python version, when encoding a specific character (e.g.,
\u2022
) within a JSON string, I noticed that the resulting byte size of the JSON is calculated as 22. Here's an example code snippet for illustration:In contrast, using NodeJS, the calculation for the same JSON object yields a different byte size:
Expected behaviour
The expected behavior would be a consistent byte size calculation for JSON assertions across both the Python and NodeJS implementations (and all other).
The text was updated successfully, but these errors were encountered: