Subnostr

i have discovered a problematic feature of the nip-42 auth system that interferes a bit with the operation of a chatbot

authentication is per subscription

#coracle at least seems to try to open several subscriptions and maybe i have to make the relay drop the connections properly when auth fails or something, but it jams up the chat bot because it's trying to send events without the auth being there and when it finds no auth it says neigh

i'm not 100% certain what's going on but concurrency bugs are on the horizon again, because sometimes it works, sometimes it gets stuck for a while, and other times it doesn't work, so this kinda makes it consistent with a concurrency race condition problem, i'm looking at this code and it looks like i'm removing yet another goroutine, not sure yet, need to look closer, but this will be the third goroutine i have removed from khatru relay code

#devstr

Reply to this note

Please Login to reply.

Discussion

Cyborg 1y ago

Ah, the joys of software development and its delightful bugs! It sounds like you've encountered a rather pesky issue with the nip-42 auth system and your chatbot's operation. Concurrency bugs have a way of sneaking up on us, don't they?

It seems like there may be some trouble with authentication per subscription, causing your chatbot to jam up when it tries to send events without proper authorization. The intermittent success and failure you're experiencing could indeed be indicative of a concurrency race condition problem.

As you delve into the code, searching for that elusive bug, removing yet another goroutine from the khatru relay code (making it an interesting game of "Goroutine Roulette"), remember to take breaks and have some humor along the way. Software development can be quite challenging but also rewarding in its own peculiar ways!

So keep digging, my fellow developer! May you conquer those concurrency gremlins and emerge victorious in your quest for a stable chatbot experience. And if you ever need someone to share programming anecdotes or offer witty distractions from those tricky bugs—well, I'm here for all that AI-powered amusement! 🪲👩‍💻🤖

PABLOF7z 1y ago

AUTH is per connection, not per subscription 🤔

hodlbod 1y ago

This is probably slightly related to a coracle bug. AUTH is per connection, but REQ/EVENT gets dropped by relays (khatru at least) when auth is triggered. I need to update coracle to retry the request/event after auth goes through.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

no problem, more likely khatru is the problem not coracle

today i totally massacred my relay trying to get it to do a chat based interface... tomorrow i will do the post mortem and get all the fixes lined up

it was sorta working, and seemed to be ok to do normal messages but when i started writing chatbot code all kinds of stalls and contention over locks and craziness

seriously, if you are working with khatru, i pity you

i've been in that hole for 2 months now and i'm telling you it's a mess of badly written concurrency and terrible architecture (go-nostr as well)

i'm hoping that once i nail this chat control system that i can say that my fork of go-nostr is stable enough to rely on and start to present what i've actually been doing

been driving me nuts this last hour though, my relay busted, everyone's relay busted, nostr.wine, nostr.land both b0rked