Richard Moore comments

Results 530 comments of


                                            Richard Moore

support for extended eth_subscribe logs

Ethers normalizes the event responses (such as converting tx values to BigInt, validating addresses, etc), so it needs to know more about the supported events. I can add new events...

support for extended eth_subscribe logs

The `RawFilter` (I’ve renamed it from Verbose ;)) will certainly allow it. I’d also like to find out which networks and which nodes support the various formats for pending things....

Did the 'error' event listener get removed in v6, like provider.on('error', () => {})?

This will be added in the next minor version. I'm currently trying to figure out the best way to abstract all the possible ways things can go wrong, so an...

Did the 'error' event listener get removed in v6, like provider.on('error', () => {})?

It’s fixed in main, but not published yet. There are two small issues I want to include in the minor bump that fixes this. Should be published on npm soon.

Did the 'error' event listener get removed in v6, like provider.on('error', () => {})?

Added in [v6.4.0](https://github.com/ethers-io/ethers.js/releases/tag/v6.4.0). Thanks! :)

Did the 'error' event listener get removed in v6, like provider.on('error', () => {})?

I’ll look into this in the morning.

Using provider.on with v6 errors as filters 'expire'

Interesting. It would be nice if on expiration it uses getLogs to backfill the missing time and resubscribe the filter.

Using provider.on with v6 errors as filters 'expire'

Yeah, I'd rather just have events work forever until the provider is destroyed. One other note, I don't know if many have noticed in v6 is the ability to pause...

Using provider.on with v6 errors as filters 'expire'

@lostarchitect So, for you, there is no change. :) It was more of a note of how it is implemented internally. Since you can pause (which can disconnect) and then...

Using provider.on with v6 errors as filters 'expire'

Auto-recovery **is** planned and being worked on *now*. It just needs to be tested on various backends which have different ways of “hanging up”. But it is 100% planned and...