Yingwen

``` sqlparser::tokenizer::Tokenizer::next_token::h96a647e5f1c84413 ``` Maybe related to the parser crate or mysql service crate we use. Could you also share your logs with us? It'd be helpful if you could change...

The opensrv crate already validates the string so the input string to the parser should be valid, I think. @discord9 https://github.com/datafuselabs/opensrv/blob/66140cc266e1eb712a0821c112a3ec743f9cccd4/mysql/src/lib.rs#L619-L626

It appears that there is not enough information in the debug log 😢 I only see the parser parsing the input query. I couldn't reproduce this using the query in...

> Unfortunately I can't reproduce the problem with all logs enabled due to lack of disc space. I'll prepare all data and code. Thanks!

We guess this is caused by https://github.com/datafuselabs/opensrv/issues/49 The `next_async` may have safety problem. https://github.com/datafuselabs/opensrv/blob/3142eb545fab811bc9289091781ce6d771cf0bf7/mysql/src/packet_reader.rs#L125-L142

The exprs of fetch and limit exchange after `with_new_exprs()` https://github.com/GreptimeTeam/greptimedb/blob/59b31372aa28f95f65c6ed4b62f8d07352059860/src/query/src/optimizer/type_conversion.rs#L89-L106 It is related to datafusion.

upstream fix: https://github.com/apache/datafusion/pull/14496 I'm going to implement a workaround. Usually the limit node doesn't require the type conversion.

I created a nightly build: https://github.com/GreptimeTeam/greptimedb/actions/runs/13157240241

The error message: ``` make: *** [Makefile:206: run-it-in-container] Killed Error: Process completed with exit code 137. ```

``` TRY 4 FAIL [ 0.046s] cmd::load_config_test test_load_datanode_example_config TRY 4 FAIL [ 0.050s] cmd::load_config_test test_load_frontend_example_config TRY 4 FAIL [ 0.042s] cmd::load_config_test test_load_metasrv_example_config TRY 4 FAIL [ 0.047s] cmd::load_config_test test_load_standalone_example_config ```...