Replying to Avatar Luxas

nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe what would be the best way to pull connection logs from Nostur? I'm having issues with the past few builds almost never sending events to Nosflare relays. Using noStrudel and Damus there's no issue. So I'm wanting to see if there is something different with how Nostur sends the event to the relays. Thanks!

you may find something in Settings -> Relay stats, if you tap on a relay it will show last errors.

or if you want to see more details you need to use Console on macOS, but the logs will probably be partially redacted unless you are in debug mode with Xcode

what are the Nosflare relays? maybe I can try and see

Reply to this note

Please Login to reply.

Discussion

Thanks! You can test wss://relay.nosflare.com

I havent noticed any issues with sending events yet, but I do get a lot of “["NOTICE","Error fetching events: Too many subrequests."]” from relay.nosflare.com

I got a message not sent today but there was nothing how to resolve it (e.g. retry button, just the yellow symbol).

I did the reply (to Will) with Damus and after coming back it had send it.

Haven’t seen that before and was posting and replying a few minutes prior without issues.

Ok I think I figured it out. Nostur sends a huge amount of REQs immediately upon sending an EVENT and it was overloading the worker before it could async save the note.

Hmm I’ll check why its sending many REQs after EVENT

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}]

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

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

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?

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

test

test 2

test 3