A NACK call incorrectly results in an ACK on the server side

[Tofuburger]

I would use the pool channel and unfortunately, I cannot send a nack to the server. On the contrary, the sent NACK becomes an ACK on the server. The client-side ACK logic works.

const req = {
  headers: {
    ack: 12345
    'message-id': 12345,
    subscription: 1
  }
};

An ACK call results in an ACK on the server. > Success

async _ack(channel, req) {
  return new Promise((resolve) => {
    channel.ack(req, undefined, undefined, (err) => {
      err
        ? reject(err)
        : resolve(req);
    });
  });
}

A NACK call incorrectly results in an ACK on the server. > Wrong Success

async _nack(channel, req) {
  return new Promise((resolve) => {
    channel.nack(req, undefined, undefined, (err) => {
      err
        ? reject(err)
        : resolve(req);
    });
  });
}