This` patch introduces a stringified version of the status in sqPoller. Instead of showing status codes such as 127, 200 etc., it shows strings such as "Command Not Found", "OK" etc. To this end, we've replaced the column status with an augmented column, statusStr, that contains the status string. Command filters such as "status=fail" work as before.
In addition, query-str didn't work correctly for sqPoller. This patch makes it function like the other commands.
Test inclusion requirements
all sqPoller tests have been updated, including sqPoller describe.
Discussion: Benefits and Drawbacks
The change is backwards-compatible, except for the bug fix to query-str which makes it function like the other commands.
Proposed Release Note Entry
sqPoller show now shows a status string instead of a numeric code, making it easier for users to understand what the error is in polling.
[X] I have read the comments and followed the CONTRIBUTING.md.
[X] I have explained my PR according to the information in the comments or in a linked issue.
[X] My PR source branch is created from the develop branch.
This` patch introduces a stringified version of the status in sqPoller. Instead of showing status codes such as 127, 200 etc., it shows strings such as "Command Not Found", "OK" etc. To this end, we've replaced the column status with an augmented column, statusStr, that contains the status string. Command filters such as "status=fail" work as before.
In addition, query-str didn't work correctly for sqPoller. This patch makes it function like the other commands.
Test inclusion requirements
all sqPoller tests have been updated, including sqPoller describe.
Discussion: Benefits and Drawbacks
The change is backwards-compatible, except for the bug fix to query-str which makes it function like the other commands.
Proposed Release Note Entry
sqPoller show now shows a status string instead of a numeric code, making it easier for users to understand what the error is in polling.
developbranch.developbranch.--signoffapplied