Subj : MsgBase get_all_msg_headers issue To : Nightfox From : Digital Man Date : Fri Mar 15 2019 12:13 am Re: MsgBase get_all_msg_headers issue By: Nightfox to Digital Man on Thu Mar 14 2019 08:12 pm > Re: MsgBase get_all_msg_headers issue > By: Digital Man to Nightfox on Wed Mar 13 2019 04:41 pm > > >> var tmpHdrs = msgbase.get_all_msg_headers(); > > >> This is the error they're seeing: > >> !JavaScript ../xtrn/DDMsgReader/DDMsgReader.js line 14211: Error: > >> index read (10710) failed > > DM> It should be fixed now. I was able to repro by just calling > DM> msgbase.get_all_msg_headers() twice in a row (the second attempt failed > DM> with the same/similar error). > > I updated my Synchronet binaries with the ones built today (March 14), but > now I'm seeing a similar error on my BBS when my reader is calling > get_all_msg_headers(): > > !JavaScript ../xtrn/DigDist/MsgReader/DDMsgReader.js line 1392: Error: > index re > ad (1062) failed > > I wasn't seeing that before. I've overwritten my binaries now, so I'm not > sure offhand which binaries I had where I wasn't seeing that error. The problem I fixed in js_msgbase.c rev 1.230 (Mar-13-2019 UTC) was introduced in rev 1.226 of js_msgbase.c (Feb-12-2019). Calling any JS MsgBase method that read from the index file before calling the get_all_msg_headers() method would cause the error. I confirmed the error and the fix. > Where it's failing in my script, I'm not calling that function twice, it's > right after opening the messagebase. That's weird. Calling get_msg_headers() right after opening the messagebase did not cause any error for me, nor should it have (the file pointer would be at the beginning the file by default). I wrote a simple little script to executing JSexec to 1. reproduce the error and 2. confirm the fix. digital man This Is Spinal Tap quote #29: I find lost luggage. I locate mandolin strings in the middle of Austin! Norco, CA WX: 54.9øF, 25.0% humidity, 4 mph E wind, 0.00 inches rain/24hrs .