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
Currently fjage_msg_add_float_array() function is used to set array values in a message. This function does base64 encoding of the array. However, the base64 encoding in the JSON message might be incorrect. Here is an example when trying to set node.location:
The array is base64 encoded in the JSON message that is sent when we set node.location using fjage C APIs shown here:
The encoding was not incorrect, as we do allow bare base64 array encoding in the specifications (although we configure the Java end to always include class information).
Added 2 fixes to improve compatibility though: bbb3691 -- to handle non-b64 encoded arrays in C gateway (was a bug) c6a3b8d -- to include clazz information in b64 encoded arrays from C gateway (enhancement)
Currently
fjage_msg_add_float_array()
function is used to set array values in a message. This function does base64 encoding of the array. However, the base64 encoding in the JSON message might be incorrect. Here is an example when trying to setnode.location
:The array is base64 encoded in the JSON message that is sent when we set
node.location
using fjage C APIs shown here:whereas, if I use a groovy shell remotely to set
node.location
(this works as expected), the JSON message that is sent isThe text was updated successfully, but these errors were encountered: