Same problem here, had to revert to from 2.3.7 to 2.3.5 and the problem is gone. I tested 2.3.6 and problem occurs too. Something changed since 2.3.6.

My setup is: Linq2DB 5.4.1 + MySQL InnoDB Cluster 8.0.35 + ProxySQL version 2.5.5-10-g195bd70, codename Truls.

We've also observed Packet received out-of-order. Expected 2; got 1. error with MySqlConnector versions 2.3.6, 2.3.7.
Adding Pipelining = False; to connection string (as mentioned in Release notes) resolved the issue, yet breaking changes like this in minor updates seem undesirable.

MariaDB (ver. 10.6.16-MariaDB-log)
MySqlConnector versions: 2.3.6, 2.3.7

Is this problem reproducible? Is it possible to provide a packet capture from when the problem occurs?

Same problem happened. 2.3.7 or 2.3.6 and mysql8.0.26 throw error "MySqlConnector.MySqlProtocolException: Packet received out-of-order. Expected 1; got 2." 2.2.5 is ok.

Is this problem reproducible? Is it possible to provide a packet capture from when the problem occurs?

This is what you need ?
ddd.txt

We've also observed Packet received out-of-order. Expected 2; got 1. error with MySqlConnector versions 2.3.6, 2.3.7. Adding Pipelining = False; to connection string (as mentioned in Release notes) resolved the issue, yet breaking changes like this in minor updates seem undesirable.

MariaDB (ver. 10.6.16-MariaDB-log) MySqlConnector versions: 2.3.6, 2.3.7

This totally fix the problem for me! Thank you!

This is what you need ?
ddd.txt

That file shows:

-> Packet Number: 0, Statement: set session transaction isolation level repeatable read;
-> Packet Number: 0, Statement: start transaction;
<- Packet Number: 1, Response Code: OK Packet (0x00) 
<- Packet Number: 2, Response Code: OK Packet (0x00) 

This is an incorrect response from the MySQL Server and is causing the error.

Adding Pipelining = False; to connection string

That is also what I would recommend given the observed behavior above.

@EmaX093

You've mentioned both of these MySQL Servers in different comments:

My setup is: Linq2DB 5.4.1 + MySQL InnoDB Cluster 8.0.35 + ProxySQL version 2.5.5-10-g195bd70, codename Truls.

MariaDB (ver. 10.6.16-MariaDB-log)

Are you using both of them? Do both exhibit the "Packet received out-of-order" problem?

@EmaX093

You've mentioned both of these MySQL Servers in different comments:

My setup is: Linq2DB 5.4.1 + MySQL InnoDB Cluster 8.0.35 + ProxySQL version 2.5.5-10-g195bd70, codename Truls.

MariaDB (ver. 10.6.16-MariaDB-log)

Are you using both of them? Do both exhibit the "Packet received out-of-order" problem?

Hello! That was the other guy, I only have MySQL InnoDB Cluster with a proxysql in front.

Anyway i just tried to connect directly to mysql without proxysql and it works just fine so is a problem related to proxysql.

Thank you for your time and I apologize for the inconveniences.

Just here to say that I'm having the exact same issue. Our MySql servers are in a cluster environment, for what it's worth. Adding Pipelining = False to connection string corrects the issue for me.

Just here to say that I'm having the exact same issue. Our MySql servers are in a cluster environment, for what it's worth. Adding Pipelining = False to connection string corrects the issue for me.

Adding to this. Our DEV tier is a single node instance with no issues @ 2.3.7. Our UAT and PRD tiers are 3-node Galera clusters that saw compatibility issues. Adding Pipelining = False; also fixed this for us.