-
Notifications
You must be signed in to change notification settings - Fork 15
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
C API support for setting parameters which are arrays #60
Comments
So this should be an issue on fjåge to fix? |
The corresponding issue in fjage is captured here: org-arl/fjage#210 This issue is just to capture the need for implementing the API |
org-arl/fjage@c6a3b8d adds type information in JSON now. However, not including it should have worked, as the specification allows it and the regression tests for it pass. What was the problem you were facing? Was it only on the latest fjåge |
The problem was when I was trying to set the I was testing this earlier with the latest dev. However, I will test it out again with your recent above-mentioned fixes. |
Was there any error in the logs when you set it using |
I did not see any error in the log file when I set it using Steps to reproduce
Expected result:
Actual result:
JSON message sent out to master container:The JSON message (
Response JSON message from master container:The JSON message (
|
The problem is the data type. |
In UnetSocket C APIs, we currently do not have support for setting parameters that are arrays. In order to do this, here is a suggested implementation of API:
Currently, this implementation of API creates a JSON message which is incorrect. This is because of the way
fjage_msg_add_float_array()
adds the array. The array is base64 encoded but its type information is not included in the JSON.The text was updated successfully, but these errors were encountered: