Can events arrive out-of-order block-wise (due to ethers.js) over a websocket connection?

[dontrolle]

Version: ethers.js 5.7.2

Hi,

I've looked in the docs and in the discussions and can't seem to find a clear answer to the following:

I'm using an ethers.js websocket connection to listen to a set of events from a contract with a single .on() listener - with a single filter that matches the events, I'm interested in.

I'm fixing a problem in a current bit of code, and have become unsure whether I need to also handle that events may arrive out-of-order across blocks? That is, can it happen that my event-listener will be invoked with events

1. from block no. X,
2. then from block no X+1, and
3. then later from block no X again?

(I am, of course, assuming that my node-provider Alchemy sends all events for block X before sending event from block X+1.)

Alternatively, what I'd really like is to receive an array of all events (that match my filter) from block X, in one fell sweep. Sort of like what getLogs() does, but with a subscription rather than synchronously.

But I don't think that this is possible with the ethers.js V5?