From NuSkooler@21:1/121 to All on Tue Nov 17 19:25:43 2020
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!
From pokeswithastick@21:2/159 to NuSkooler on Thu Nov 19 09:07:39 2020
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.
From pokeswithastick@21:2/159 to NuSkooler on Thu Dec 3 09:48:35 2020
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)
From pokeswithastick@21:2/159 to NuSkooler on Sun Dec 6 10:12:39 2020
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.