[ES|QL] Remove client-side parsing error log (#217114)

## Summary

We used to log all parsing errors for diagnostic purposes when since
they were never expected to happen.

With
21845ad7a1
they became much more common, especially while editing queries, because
of ANTLR stack popping exceptions (see
https://github.com/elastic/elasticsearch/issues/119025).

We should stop logging them all to the console... it makes it look like
something is wrong.

Query to test with:
`FROM kibana_sample_data_* 
| WHERE @timestamp != )`
This commit is contained in:
Drew Tate 2025-04-04 08:03:11 -06:00 committed by GitHub
parent e942404cb9
commit a1db715efe
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -149,8 +149,9 @@ export const parse = (text: string | undefined, options: ParseOptions = {}): Par
return { root, ast: commands, errors, tokens: tokens.tokens };
} catch (error) {
// eslint-disable-next-line no-console
console.error(error);
if (error !== 'Empty Stack')
// eslint-disable-next-line no-console
console.error(error);
const root = Builder.expression.query();