• View extended file info

    From Accession@1:103/705 to All on Mon Sep 18 20:29:14 2023
    Hello,

    Is 'shell.view_file_info(FI_INFO)' something hard coded? If so, can someone point me to which file I should try to update or check on before posting an issue (that's probably my own fault, or something related to using Archlinux) on gitlab?

    I'm getting a segfault and coredump when hitting "E" from my transfer menu, but I don't think I've modified anything regarding that. Just wondering if it's some file that I stuck somewhere that didn't get updated with everything else. I've tried the command on Vert and it works as expected, so rather that try to file a bug, I should probably look for *my* bug. :)

    Regards,
    Nick

    ... Common sense is instinct. Enough of it is genius.
    ---
    ž Synchronet ž thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Accession on Mon Sep 18 21:10:37 2023
    Re: View extended file info
    By: Accession to All on Mon Sep 18 2023 08:29 pm

    Hello,

    Is 'shell.view_file_info(FI_INFO)' something hard coded? If so, can someone point me to which file I should try to update or check on before posting an issue (that's probably my own fault, or something related to using Archlinux) on gitlab?

    I'm getting a segfault and coredump when hitting "E" from my transfer menu, but I don't think I've modified anything regarding that. Just wondering if it's some file that I stuck somewhere that didn't get updated with everything else. I've tried the command on Vert and it works as expected, so rather that try to file a bug, I should probably look for *my* bug. :)

    I think someone just recently posted about this problem on (your?) BBS. It looked like the ctrl/text.dat file was not updated when the sysop upgrade to SBBS v3.19 and some of the format strings used for extended file information could cause a crash if used incorrectly. I recommend the sysop (you?) merge in those new strings from the text.dat included in v3.19.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #79:
    SyncEdit = A defunct 3rd party full-screen editor written for Synchronet
    Norco, CA WX: 74.7ųF, 62.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Accession@1:103/705 to Digital Man on Tue Sep 19 19:34:59 2023
    Re: View extended file info
    By: Digital Man to Accession on Mon Sep 18 2023 09:10 pm

    I think someone just recently posted about this problem on (your?) BBS. It looked like the ctrl/text.dat file was not updated when the sysop upgrade to SBBS v3.19 and some of the format strings used for extended file information could cause a crash if used incorrectly. I recommend the sysop (you?) merge in those new strings from the text.dat included in v3.19.

    Huh. Nobody reported it to me, but I found it out on my own testing all my commands from the file menu. Anyhew, I was definitely keeping up merging new strings, as I had the same amount as the default text.dat. However, I didn't catch the 10 or so strings that were actually changed during that time. So yes, that's where the problem was, and is now fixed. Thanks for the heads up.

    Regards,
    Nick

    ... Don`t force it, get a larger hammer.
    ---
    ž Synchronet ž thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Accession on Tue Sep 19 22:17:24 2023
    Re: View extended file info
    By: Accession to Digital Man on Tue Sep 19 2023 07:34 pm

    Re: View extended file info
    By: Digital Man to Accession on Mon Sep 18 2023 09:10 pm

    I think someone just recently posted about this problem on (your?) BBS. It looked like the ctrl/text.dat file was not updated when the sysop upgrade to SBBS v3.19 and some of the format strings used for extended file information could cause a crash if used incorrectly. I recommend the sysop (you?) merge in those new strings from the text.dat included in v3.19.

    Huh. Nobody reported it to me, but I found it out on my own testing all my

    Yeah, it was reported on the Synchronet Discussion sub:

    ŚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄśśśś
    ³ Subj: Possible file upload bug?
    ³ Attr: Replied
    ³ To : All
    ³ From: Deepthaw #840
    ³ Date: Fri Sep 15 2023 10:11 am PDT (4.5 days ago) ĄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄśśśśśś

    I was making the rounds uploading a file to "teh scene" today (go look for traxtor.zip, it's a neat DOS puzzle game made for a 2023 comp) and over on Pharcyde I hopped to the file listing to see if the file_id displayed properly and it caused a disconnect.

    https://imgur.com/a/2QSfO97

    Since I'm no longer a sysop I have no idea where the bug could be - the bbs or the software, but thought I'd share it here.

    commands from the file menu. Anyhew, I was definitely keeping up merging new strings, as I had the same amount as the default text.dat. However, I didn't catch the 10 or so strings that were actually changed during that time. So yes, that's where the problem was, and is now fixed. Thanks for the heads up.

    In hindsite, I should not have repurposed existing strings, but I wanted to try to keep that closely-related (extended file strings) close together in the text.dat. Oh well. Glad you caught it and got the solution merged quickly.
    --
    digital man (rob)

    Sling Blade quote #13:
    Karl: He lives inside of his own heart. That's an awful big place to live in. Norco, CA WX: 62.7ųF, 88.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Accession@1:103/705 to Digital Man on Wed Sep 20 16:39:15 2023
    Re: View extended file info
    By: Digital Man to Accession on Tue Sep 19 2023 10:17 pm

    Yeah, it was reported on the Synchronet Discussion sub:

    Recently even. I must not have been reading messages at that time, sometimes I skim through if I'm not involved in the current discussion. Would have been nice if he would have let me know directly, but it's all good. I came across it soon enough after.

    In hindsite, I should not have repurposed existing strings, but I wanted to try to keep that closely-related (extended file strings) close together in the text.dat. Oh well. Glad you caught it and got the solution merged quickly.

    I get it. As I was replacing them, I kinda figured that's what you were doing, since all the strings for that screen were directly above the ones that were replaced, and the ones that were removed seemed a little redundant anyways. Got it fixed up, that's what matters. I'd say it's not too bad for my text.dat being probably well over 10 years old. ;)

    Regards,
    Nick

    ... I love criticism just so long as it's unqualified praise.
    ---
    ž Synchronet ž thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)