1. Forum
  2. DOVE-Net
  3. Synchronet Sysops

  • forcereplace in tickit.ini is no longer working.

    From Nigel Reed@VERT to GitLab issue in main/sbbs on Sat Apr 10 09:23:19 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/251

    This is a regression issue. It was working perfectly fine and now it's broken.

    tickit.ini entry
    [FMLYDAIL]
    Dir=FNFMLYDAIL
    Handler=tickit/nodelist_handler.js
    HandlerArg={"domain":"fmlynet" ,"match":"FMYDAILY.Z*", "nlmatch":"FMYDAILY.*"} Forcereplace = 1

    When running tickit.js
    "Z8DAILY.099" already exists in "/sbbs/data/dirs/familynet/fnfmlydail/", but has no matching Replaces line


    Same for a different area.
    [PASPOINT]
    Dir=PASPOINT
    Forcereplace = 1

    Working with 'ppoint.z99' in 'PASPOINT'.
    Moving /sbbs/fido/inbsecure/ppoint.z99 to /sbbs/data/dirs/pascalnet/paspoint/. "ppoint.z99" already exists in "/sbbs/data/dirs/pascalnet/paspoint/", but has no matching Replaces line


    The -force-replace command line still works, so this needs fixing so the Forcereplace parameter in tickit.ini is picked up again.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab note in main/sbbs on Sun Apr 11 04:05:10 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/251#note_1934

    Set it to "true" instead of "1".

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab issue in main/sbbs on Sun Apr 11 04:32:54 2021
    close https://gitlab.synchro.net/main/sbbs/-/issues/251

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab note in main/sbbs on Sun Apr 11 04:32:54 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/251#note_1935

    So it looks like way that Mark Lewis originally wrote that feature, any value other than "undefined" was considered true (enabled) - so even /false/ would have been considered the same as true. So I fixed that and the value must now be /true/ for that feature to enabled. tickitcfg.js should be writing true or false to the tickit.ini file and nothing else (for that setting/key).

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From waldo kitty@VERT to GitLab note in main/sbbs on Mon Apr 12 01:33:00 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/251#note_1939

    i'm just catching up... sorry for being late to the party...

    yeah, tickitcfg was pretty bare bones when i picked it up to enhance it to work with the updates in tickit... i was also still pretty new at the whole js programming stuff... there's a huge nul out there when looking for server side js stuff... everything expects to be running in a browser...

    anyway, i don't doubt there are bugs like that... i wasn't sure when to use 0/1 or false/true or which was which even... there's probably a similar bug in tickit which is why those debug lines at the beginning of the output for each area listing which address they'll be using... looking at the link you provided on IRC, those are LOG_DEBUG lines and should not be written unless debugging is turned on for tickit...

    anyway, i just wanted to drop a quick note that it was a noob error and i was having to figure out not only the language but also two or three other folks' code and intentions... IIRC nelgin added the force-replace stuff but it needed expanding with the new features in tickit and i was kinda the only one testing anything...

    sorry for the rambling... it has been a long long long week today... and my apologies for both the bug and the ramble...

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Nelgin@VERT/EOTLBBS to waldo kitty on Mon Apr 12 05:50:41 2021
    waldo wrote:
    https://gitlab.synchro.net/main/sbbs/-/issues/251#note_1939
    anyway, i just wanted to drop a quick note that it was a noob error and i was having to figure out not only the language but also two or three other folks' code and intentions... IIRC nelgin added the force-replace stuff but it needed expanding with the new features in tickit and i was kinda the only one testing anything...

    Yes, not sure why DM is blaming you for it. The CVS log shows that I submitted the forcereplace code, but like you, I was fumbling around so, it is what it is. It'd have been nice if there was a note to say it had been "fixed".

    ---
    þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
  • From Digital Man@VERT to Nelgin on Mon Apr 12 07:29:54 2021
    Re: Re: forcereplace in tickit.ini is no longer working.
    By: Nelgin to waldo kitty on Sun Apr 11 2021 10:50 pm

    waldo wrote:
    https://gitlab.synchro.net/main/sbbs/-/issues/251#note_1939
    anyway, i just wanted to drop a quick note that it was a noob error and i was having to figure out not only the language but also two or three other folks' code and intentions... IIRC nelgin added the force-replace stuff but it needed expanding with the new features in tickit and i was kinda the only one testing anything...

    Yes, not sure why DM is blaming you for it. The CVS log shows that I submitted the forcereplace code, but like you, I was fumbling around so, it is what it is. It'd have been nice if there was a note to say it had been "fixed".

    I think you're confusing your -force-replace option with the "forcereplace" area key. The "forcereplace" area key was added via a patch provided by Mark:
    http://cvs.synchro.net/cgi-bin/viewcvs.cgi/exec/tickit.js?r1=1.52&r2=1.53
    --
    digital man

    Synchronet "Real Fact" #43:
    Synchronet added Baja/PCMS support with v2.00a (1994).
    Norco, CA WX: 53.8øF, 92.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net