Replying to Avatar Fabian

I think there may be an issue with missing EOSEs. Nostur sends a CLOSE after receiving EOSE but for some REQs (not all) on nosflare there is never an EOSE and its probably kept open and hitting the limit of 50, Nostur normally never has that much subscriptions open at the same time.

Example REQ that didn’t receive EOSE:

["REQ", "A4CB2EF4-5DB8-4D74-BF6B-9B860DA44777", {"ids": ["5119271f7af3847dd2c655f6a5cfb1448bb3a70edf52acec4f39844346917cca"], "limit": 500}]
Avatar
Luxas 1y ago

Hey thanks for pointing out that issue! I have resolved it. 🙌

Reply to this note

Please Login to reply.

Discussion

Avatar
Fabian 1y ago

do you know who is behind relay.nostraddress.com? I’m getting the same issue from that relay and also some new ones: Unsupported filter: since / until

Avatar
Luxas 1y ago

Hey! Yes that's me as well. Have been testing blocking those filters as they aren't technically supported due to the object store nature of Nosflare. But they should be sending correct EOSE now, right?

Avatar
Fabian 1y ago

I think so, I’ll let you know if I see those limit errors again