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
There is a number of errors like this, mentioning schema errors for an attribute value in a StatusResponse, e.g. /sS/1/s, type:
2024-12-20T00:42:16.601Z 49360 KTT+TC=101TC001 KTT+TC=101TC001 92cd Received invalid StatusResponse schema errors: /sS/1/s, type, , /sS/1/s, string, {"mType":"rSMsg","type":"StatusResponse","mId":"92cd7fb0-eeec-4e68-8b62-8b5c323308bc","sTs":"2024-12-20T00:41:58.235Z","ntsOId":"KTT+TC=101TC001","xNId":"","cId":"KTT+TC=101TC001","sS":[{"sCI":"S0007","n":"status","q":"recent","s":"True"},{"sCI":"S0007","n":"intersection","q":"recent","s":1}]}
The problem is this part:
"s":1
Numbers must be send as strings, so use "s":"1" instead.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There is a number of errors like this, mentioning schema errors for an attribute value in a StatusResponse, e.g. /sS/1/s, type:
The problem is this part:
Numbers must be send as strings, so use "s":"1" instead.
The text was updated successfully, but these errors were encountered: