What is the recommended way of handling provider errors occurring in the context of contract events monitoring?

[BB-301]

I am wondering what would be the way to go about error handling for a provider instance when that instance is being used inside a contract instance for the purpose of event monitoring. For instance:

import * as ethers from "ethers";

const RPC_URL: string = "<rpc url here>";
const CONTRACT_ADDRESS: string = "<address here>";
const ABI: string[] = [
    "event Transfer(address indexed from, address indexed to, uint amount)"
];

const provider = new ethers.JsonRpcProvider(RPC_URL);
const contract = new ethers.Contract(CONTRACT_ADDRESS, ABI, provider);

contract.on("Transfer", (from, to, amount, _event) => {
    console.log(`${from} transferred ${amount} to ${to}`); 
});

When all goes well, this code is fine, but what happens if I want to monitor provider errors, such as, for instance, an RPC server that returns a 429 status code while the event subscription is performing some polling? What would be the way of handling such errors to avoid process termination?

I have tried the following:

provider.on("error", error => {
    console.log(`An error occurred: ${error.message}`);
});

but that callback does not appear to get called when such an error occurs. So far, my experience with situations like that is that the process gets terminated because of an "unhandled" error.

There must be a way to handle those kinds of errors (i.e., errors occurring while "listening" for contract events that have been registered using the contract instance's ".on" method). Any help would be greatly appreciated! Thanks. :)

Edit: I'm using version 6.11.1

[C0D3O]

I confirm, I guess no error are being catched with the listener. The logic with provider error handling seems to be missing almost completely, except for the message 'trying to reconnect in 1s", which does nothing

[larrettgee]

Wondering if there are any updates here. I'm using a node that occasionally acts up, so being able to handle errors in my contract.on would be super helpful instead of getting flooded with logs