• Bug Fixes

    From NuSkooler@21:1/121 to All on Tuesday, November 17, 2020 19:25:42
    A set or fairly major (and related) bugs around message importing that have somehow snuck under the radar for a loooong time have been fixed and pushed to master:

    * Fix TZUTC/TZUTCINFO kludge processing
    * Fix message timestamp when recording to database
    * Fix a byte length issue when processing messages if TZUTC is set where we might actually skip other messages in a packet for import!

    All users are encouraged to update!


    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From deepthaw@21:2/128 to NuSkooler on Tuesday, November 17, 2020 20:55:10
    132
    Installed and working great here. Given all the %RESCAN's I've done recently, I'm sure my hubs hate me, but I did one more to fix all the dates.

    On 11/17/2020 7:25 pm NuSkooler said...
    A set or fairly major (and related) bugs around message importing that have somehow snuck under the radar for a loooong time have been fixed and pushed to master:




    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.0)
    * Origin: cortex (21:2/128)
  • From NuSkooler@21:1/121 to deepthaw on Tuesday, November 17, 2020 21:25:58
    On Tuesday, November 17th deepthaw was heard saying...
    Installed and working great here. Given all the %RESCAN's I've done recently, I'm sure my hubs hate me, but I did one more to fix all the dates.

    I think most if not all the hubs you're hitting are on modern hardware and probably didn't even notice ;)

    Glad it's working well!


    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@21:2/159 to NuSkooler on Thursday, November 19, 2020 09:07:38
    132
    On 18/11/2020 2:27 am NuSkooler said...
    * Fix TZUTC/TZUTCINFO kludge processing * Fix message timestamp when recording to database * Fix a byte length issue when processing messages if TZUTC is set where we might actually skip other messages in a packet for import!

    Upgraded here too. I wonder if that's why every so often my ftn_in folder stops being processed until I restart Enigma.

    --- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)
  • From NuSkooler@21:1/121 to pokeswithastick on Thursday, November 19, 2020 13:10:10
    On Thursday, November 19th pokeswithastick said...
    Upgraded here too. I wonder if that's why every so often my ftn_in folder stops being processed until I restart Enigma.

    Hm, that sounds like something else most likely. If you see that again and can capture logs I can take a look.


    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@21:2/159 to NuSkooler on Friday, November 20, 2020 14:19:42
    132
    On 19/11/2020 1:10 pm NuSkooler said...
    Hm, that sounds like something else most likely. If you see that again and can capture logs I can take a look.

    Sure will do

    --- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)
  • From pokeswithastick@21:2/159 to NuSkooler on Thursday, November 26, 2020 09:16:16
    On 20/11/2020 2:19 pm pokeswithastick said...
    Hm, that sounds like something else most likely. If you see
    that again and can capture logs I can take a look.

    Sure will do

    Ok it happened again and I've submitted a bug report on github #329. Seems to give up unzipping a .ZIP file

    --- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)
  • From pokeswithastick@21:2/159 to NuSkooler on Thursday, December 03, 2020 09:48:34
    On 26/11/2020 9:16 am pokeswithastick said...
    Ok it happened again and I've submitted a bug report on github #329. Seems to give up unzipping a .ZIP file

    Interestingly the unzip command PID doesn't have any arguments listed in /proc/(pid)/cmdline.

    I've overriden to the config to try and make enigma use 7zip for zip archives and I'll see what that does. Otherwise I'll write a shell script wrapper around unzip to try and capture inputs and outputs and see where it stops (presumably waiting for input as you said)

    --- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)
  • From NuSkooler@21:1/121 to pokeswithastick on Thursday, December 03, 2020 13:51:16
    On Thursday, December 3rd pokeswithastick said...
    Interestingly the unzip command PID doesn't have any arguments listed in /proc/(pid)/cmdline.

    If you really want (and maybe I should just push a change for trace level logging) archivers.js could just log the thing.

    I'm not clear how we'd end up without parameters though -- unless unzip is clearing them (which in Linux you can certainly do).



    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@21:2/159 to NuSkooler on Sunday, December 06, 2020 10:12:38
    132
    On 03/12/2020 6:51 am NuSkooler said...
    If you really want (and maybe I should just push a change for trace level logging) archivers.js could just log the thing.

    Thanks but I can probably patch the code locally if I need to. So far though it has been ok with using 7Zip. I think you are probably right that unzip is waiting for user input for some reason. I wonder if because I have 2 containers (binkd & enigma) sharing a mail directory (local fs mounted into each container) that this causes some conflict like the files being partially written by binkd but immediately visible to enigma so the import routine runs but on locked/corrupted files.

    If it happens with 7Zip I'll investigate more.

    --- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)
  • From NuSkooler@21:1/121 to pokeswithastick on Sunday, December 06, 2020 14:00:18
    Twas Sunday, December 6th when pokeswithastick said...
    If it happens with 7Zip I'll investigate more.

    Just a warning on 7zip: Some builds result in "volume not found" errors when processing zip files.



    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@21:2/159 to NuSkooler on Tuesday, December 08, 2020 11:29:34
    On 06/12/2020 7:00 am NuSkooler said...
    Just a warning on 7zip: Some builds result in "volume not found" errors when processing zip files.

    Ah yes I read that in the change log

    --- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)