Fatal `Packets out of order` exception using `mysql` lib connecting to `mysql2` proxy

Using the example proxy, when making a client connection using the mysql library, a fatal exception occurs and the connection is lost.

Client example:

const knex = require("knex")({
  client: "mysql",
  connection: {
    host: "127.0.0.1",
    port: 4000,
    user: "***",
    password: "***",
    database: "***"
  },
});

knex.raw("select 1").then(console.log);

The server exception:

[nodemon] starting `node index.js`
connection
Warning: got packets out of order. Expected 3 but received 0
proxying query: select 1
events.js:298
      throw er; // Unhandled 'error' event
      ^

Error: Connection lost: The server closed the connection.
    at Socket.<anonymous> (/foo/node_modules/mysql2/lib/connection.js:91:31)
    at Socket.emit (events.js:321:20)
    at TCP.<anonymous> (net.js:668:12)
Emitted 'error' event on Connection instance at:
    at Connection._notifyError (/foo/node_modules/mysql2/lib/connection.js:221:12)
    at Socket.<anonymous> (/foo/node_modules/mysql2/lib/connection.js:97:12)
    at Socket.emit (events.js:321:20)
    at TCP.<anonymous> (net.js:668:12) {
  fatal: true,
  code: 'PROTOCOL_CONNECTION_LOST'
}

Client exception:

(node:1521) UnhandledPromiseRejectionWarning: Error: Packets out of order. Got: 4 Expected: 1

NOTE: This does not occur when using mysql2 as the client library.

Please let me know if I can provide any further detail to help debug.

[haganbt]

@dtikhonov-iex see https://github.com/sidorares/node-mysql2/issues/528#issuecomment-944949065 also.

[dtikhonov-iex]

Thanks for this workaround, @MartinGassner. I was hoping that the bug was something obvious (and I spent some time reading the code trying to figure it out), but from @sidorares’s description it seems that this is a structural issue.