MQTT over WebSocket, QoS 0 messages may not get sent before disconnection

[ysfscream]

Describe the bug
When using MQTT over WebSocket with QoS set to 0, I have encountered a situation where the publish callback is triggered before the message has been successfully sent. This causes the message not to get sent before the connection is ended. This issue occurs intermittently only with WebSocket connections, not with MQTT over TCP connections.

To Reproduce
Here is a simple code snippet that reproduces the issue:

const client = // initialize MQTT client with WebSocket
client.publish(topic, message, { qos: 0 }, (err, packet) => {
  if (err) {
    console.error('Publish failed:', err)
  } else {
    console.log('Publish succeeded:', packet)
    client.end()
  }
})

In the case of a WebSocket connection and QoS 0, the 'Publish succeeded' log may print before the message is actually sent.

Expected behavior
The publish callback should not be called until the message is successfully sent, even when using WebSocket and QoS 0.

Environment (please complete the following information):

• OS: macOS
• Node.js version: v16.14.2
• MQTT.js version: 4.3.7

Additional context
The issue only occurs intermittently and with WebSocket connections, not other MQTT/TCP of connections.

[robertsLando]

Could you submit a PR to fix this issue?

[robertsLando]

MQTT 5.0.0 BETA is now available! Try it out and give us feedback: npm i mqtt@beta. It may fix your issues

[github-actions]

This is an automated message to let you know that this issue has
gone 365 days without any activity. In order to ensure that we work
on issues that still matter, this issue will be closed in 14 days.

If this issue is still important, you can simply comment with a
"bump" to keep it open.

Thank you for your contribution.

[github-actions]

This issue was automatically closed due to inactivity.