Nostr Web Client

Did it show a timeout from one of the relays after 10s whilst showing success from the others before moving on to complete the rest of the command?

The timeout is usually a failure to connect to the relay, or less likely, a failure to receive the EOSE event.

Yonle 1y ago

as i configure to only connect to bouncer relay, it only times out waiting for events to be received.

Reply to this note

Please Login to reply.

Discussion

DanConwayDev 1y ago

Is bostr definately sending thr EOSE event?

Is the error reproducable? What would should I follow to do so?

Kudos for checking out the request to investigate why it might be failing.

Yonle 1y ago

it sends once it ensures that all relays sended EOSE, which may be slow but the only effective way to do it.

DanConwayDev 1y ago

Could it be that the EOSE event is not sent until after the timeout. I'm finding that its common for a least one relay to timeout but not consistently the same one.

DanConwayDev 1y ago

I think most clients must factor this into their design and don't rely so much on waiting for a EOSE.

It should just timeout and move to the next step.

I don't have any integration tests built for this scenario.

Yonle 1y ago

yep. the eose did not sent.