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
Neu3 task protocol uses a double type to encode and decode body IDs in JSON objects. It can cause ID overflow in some situations, especially when the ID is tar encoded. Using double is not safe anyway because the ID type is uint64 and expected to be valid in the positive range of int64 in real applications.
The text was updated successfully, but these errors were encountered:
I recommend that when an ID is stored in a JSON object outside of NeuTu/Neu3, it should always be decoded, i.e. using a raw ID. Encoding should be kept inside NeuTu/Neu3 and never exposed because the encoding rules are not stable.
Neu3 task protocol uses a double type to encode and decode body IDs in JSON objects. It can cause ID overflow in some situations, especially when the ID is tar encoded. Using double is not safe anyway because the ID type is uint64 and expected to be valid in the positive range of int64 in real applications.
The text was updated successfully, but these errors were encountered: