Happens when non throwing error gets sent back as stdout.

After parsing,

• Check res.status === 1
  • send res.message to toast; return;

Example response:
{
"status": 1,
"name": "Error",
"message": "\nSELECT Id, CaseNumber, ContactId.FirstName, ContactId.LastName\n ^\nERROR at Row:1:Column:24\nDidn't understand relationship 'ContactId' in field path. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names.",
"exitCode": 1,
"commandName": "DataSoqlQueryCommand",
"stack": "Error: \nSELE....",
"warnings": []
}

Error

Type error is caught but message is not surfaced;

Checklist

• Surface error message
• Test by checking Boolean field as you would a String field eg. WHERE Checkbox__c != ''

Example error response

{
"status": 1,
"name": "INVALID_FIELD",
"message": "\nCustomer_Not_Home__c FROM WorkOrder WHERE Customer_Not_Home__c != '' LIMIT\n ^\nERROR at Row:1:Column:54\nvalue of filter criterion for field 'Customer_Not_Home__c' must be of type boolean and should not be enclosed in quotes",
"exitCode": 1,
"context": "DataSoqlQueryCommand",
"etc: "..."
}

When writing a multi-line query such as

SELECT Count(Id), Account.Id FROM Contact 
WHERE Account.Id != null 
GROUP BY Account.Id

instead of in a single line, an error is thrown as the new lines are replaced as a string length 0. When spaces are added to the end of the lines, the query works correctly.

Would suggest changing the '' in

seems to be error on bigger sfdx soql calls atm.