yeah, it wasn't growing the arrays to fit what was being put into them
still got another glitch in here somewhere, probably a regression... again a forever loop in the database query code lol
idk even how it's happening, probably me putting the wrong direction <> in somewhere
i think i found it... i switched to collecting the found events in a map (key/value hash table) and i was checking the limit size based on the result variable which isn't populated until after all the event keys are retrieved
i think this will fix it
it's that kind of forever loop where your termination condition is incorrect and it keeps looping because the condition doesn't update to reflect the state of execution
btw, the point of using the maps is it allows me to automatically deduplicate in case of clients sending filters with repeating elements that yield the same event again... which probably can happen, so best to mitigate it
Oddbean new post about login | logout