ministry_of_finance node pool error about greenlight HOT 3 CLOSED

I've seen this now as well.

I believe it occurs when you try to make a connection to the node pool while it is already open.

For several services, a connection is made on page load to verify a proof request. If you try to load the page several times in quick succession you might see this.

Currently, we open and close pool and wallet connections right before and after every interaction with the wallet/ledger.

from greenlight.

Hmm. I ran into that issue on my very first time visiting that service, so I don't think it should been caused by that. Unless it was connecting to the node pool for its own reasons, and I opened the URL too quickly after it started?

Either way, that should probably be insulated a little more from the user. I would have thought that the connection pooling system should be able to handle more than one simultaneous connection though... That or reuse the existing connection to send another message, unless it's using one of ZMQ's req/rep pairs, which cannot send another message until the previous is handled.

from greenlight.

Currently, we use a context manager to open/close a connection to the wallet and ledger on a per-transaction basis.

This is very much a WIP so if you see something that can be improved, I encourage you to dig in.

from greenlight.