contract.on still fire past events

[svianney]

Ethers Version

5.7.2

Search Terms

subscribe, past events, events

Describe the Problem

First of all, Thanks @ricmoo for this package :)
I've read this issue about the problems of the event subscription function contract.on() that fires up past events. It seems that this bug have been fixed in the 5.7+ version. However I'm still experiencing the issue on the BSC.
Is this a bug ?

Thanks for your time

Code Snippet

contract.on(contract.filters.Mint(), (sender, amount0, amount1, ...args) => {});

Contract ABI

[
  {
    "anonymous": false,
    "inputs": [
      {
        "indexed": true,
        "internalType": "address",
        "name": "sender",
        "type": "address"
      },
      {
        "indexed": false,
        "internalType": "uint256",
        "name": "amount0",
        "type": "uint256"
      },
      {
        "indexed": false,
        "internalType": "uint256",
        "name": "amount1",
        "type": "uint256"
      }
    ],
    "name": "Mint",
    "type": "event"
  }
]

Errors

As mentionned above, I'm still experiencing the issue of the past events being fired up.

Environment

node.js (v12 or newer), Other (please specify)

Environment (Other)

NodeJS 18, QuickNode RPC Provider, BSC mainnet

[ricmoo]

Can you provide more info? Like how far in the past? The current blockNumber and the blockNumber of the events? What backend you are using, etc.

[svianney]

I'm sorry I've bothered you, I was experiencing this issue with an old version of Ethers, I thought I was still experiencing the issue after I have upgraded to the newest version. Turns out, this time my code at fault and my research on the Github issues misled me to think the problem was from your wonderful package.
Thank you for your fast answer, I can close the non-issue.