-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Implement fine-grained errors to cloud queries #12460
Conversation
retval = 1; | ||
w->response.code = 404; | ||
aclk_http_msg_v2_err(query_thr->client, query->callback_topic, query->msg_id, w->response.code, NULL, 0); | ||
aclk_http_msg_v2_err(query_thr->client, query->callback_topic, query->msg_id, w->response.code, CLOUD_EC_MALFORMED_NODE_ID, CLOUD_EMSG_MALFORMED_NODE_ID, NULL, 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Not specific to this PR, but maybe there could be another response than 404 to indicate this? I know cloud must already be consuming this, but maybe as an enhancement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah should be easier to change this in future after cloud consumes the new custom error codes -> so they can match it whenif we change from 404
Summary
Implements #12340
Test Plan
See the generated message. Cloud hasn't implemented this yet but we got green light to send this (Cloud should for now ignore until they find time to implement) but should not cause errors on cloud.
Additional Information