• Suspected Bug - Nodelist Compiler

    From Avon@21:1/179 to g00r00 on Sunday, September 17, 2017 14:34:57
    Hi g00r00

    Doing some work with both Caphood and Warmfuzzy on their Raspberry Pi and
    Linux 64 bit systems respectively. I've picked up on an issue I have been
    able to also reproduce this afternoon on 1/179 using my test system.

    The issue is that when MUTIL [MergeNodeLists] stanza is called to merge
    several nodelists. The corrosponding output in nodelist.txt in the data directory has some additional artifacts introduced in the file.

    These appear as control characters (or similar) in the nodelist.txt and show
    up in a dedicated line at the end of each compiled nodelist.

    The impact is seen when using the inbuilt nodelist browser. What happens is
    the /0 address for the last NET related to a nodelists Zone is duplicated.

    In the case of fsxNet I can see the following for 21:2/? as the nodelist
    search criteria:

    [snip]

    Node System Name Location SysOp

    ============ ========================== ====================================== 21:2/0 fsxNet (NET 2) Perrysburg USA Todd Zieman 21:2/100 Tholian HUB Perrysburg USA Todd Zieman 21:2/102 Cartel BBS Chattanooga USA Wes Keene 21:2/103 Resistance Pride BBS Pittsboro USA Kevin Sonney 21:2/104 Gryphus BBS Nowra AUS Stephen Arnold 21:2/105 Another F-ing BBS Maricopa USA Gary Crunk 21:2/106 Back To The Roots BBS Geneva CHE Fabian Lucchi 21:2/107 Dales BBS Gorleston GBR Dale Cousins 21:2/108 UnderZaNet BBS London GBR Jan Henkins 21:2/110 iNK tWO BBS Covina USA Lawrence Manuel 21:2/111 Leisure Time BBS New Baden USA Robert Riddell 21:2/112 The Hub BBS Watauga USA David DeWell 21:2/113 PHATstar RetroBOX BBS Ontario CAN Matthew Smith 21:2/115 Mystic Rhythms BBS San Francisco USA Rob Cole 21:2/117 The Positronium Repository Lafayette USA Ben Ritchey 21:2/118 The Llama Lounge Melbourne AUS Tim Casey 21:2/119 Temple of Doom BBS Anderson USA Kris Jones 21:2/120 The Positronium Repository Lafayette USA Ben Ritchey 21:2/121 Basement Theory BBS Sciotoville USA Josh Ramsey 21:2/123 Flower BBS Munich GER Kate Lily 21:2/124 Family Fun BBS Kamloops CAN Adam Clark 21:2/125 Fortknox BBS Emmen NLD George de Vries 21:2/126 Mastodont BBS Puerto Montt CHL Patricio Rodriguez 21:2/127 Battlestar BBS Warminster USA Mark Iezzi 21:2/128 Hack-Tic BBS Noordwijk NLD Paul Muller 21:2/129 Risky Business BBS Sudbury CAN Roger Ouimette 21:2/130 BuckeyeAZ.NET BBS Buckeye USA Dean Galloway 21:2/131 Orbit BBS Opp USA Allen Scofield 21:2/132 Springville Mill BBS Stafford Springs U Matthew Thibodeau 21:2/133 Ghost Opera BBS Ann Arbor USA Lori Holden 21:2/134 Troy's Den BBS Phoenix USA Scott Miller 21:2/135 The Last Rainboard Knoxville USA Jerry Adams 21:2/136 Deep Space'94 BBS Evansville USA Tony Toon 21:2/0

    Found 34 matches.

    [snip]

    But there really are only 33 stated addresses in NET 2.

    You'll also note there is nothing listed against the last bogus 21:2/0

    I have not seen this behaviour in Windows/32 version of Mystic.

    Others may like to check their nodelist browsers to see if they can confirm this behaviour. But hopefully this gives you enough to check out :)

    Best, Paul

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Cryptogenic Radix (21:1/179)
  • From Black Panther@21:1/186 to Avon on Saturday, September 16, 2017 20:45:20
    On 09/17/17, Avon said the following...

    These appear as control characters (or similar) in the nodelist.txt and show up in a dedicated line at the end of each compiled nodelist.

    The impact is seen when using the inbuilt nodelist browser. What happens is the /0 address for the last NET related to a nodelists Zone is duplicated.

    I can confirm this as well here with Mystic Linux/64bit. I hadn't noticed it before...


    ---

    Black Panther
    aka Dan Richter
    Sysop - Castle Rock BBS
    telnet://castlerockbbs.com
    The sparrows are flying again...

    --- Mystic BBS v1.12 A35 (Linux/64)
    * Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)
  • From Avon@21:1/179 to Black Panther on Sunday, September 17, 2017 15:02:46
    On 09/16/17, Black Panther said the following...

    I can confirm this as well here with Mystic Linux/64bit. I hadn't
    noticed it before...

    Many thanks Dan :)

    Best, Paul

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Cryptogenic Radix (21:1/179)
  • From deepthaw@21:2/136 to Avon on Sunday, September 17, 2017 08:51:40
    Knoxville USA Jerry Adams 21:2/136 Deep Space'94 BBS Evansville USA Tony Toon 21:2/0

    Actually, that's just my name. "Tony Toon\n21:2/0". My parents were really, really weird.

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)
  • From g00r00@21:1/108 to Avon on Sunday, October 22, 2017 15:40:12
    The issue is that when MUTIL [MergeNodeLists] stanza is called to merge several nodelists. The corrosponding output in nodelist.txt in the data directory has some additional artifacts introduced in the file.

    Can you give me those specific nodelists so I can try to reproduce the exact issue here?

    Sorry I know this is a very late reply and you probably won't still have that data to supply but I thought I'd ask anyway.

    --- Mystic BBS v1.12 A36 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Avon@21:1/101 to g00r00 on Monday, October 23, 2017 10:24:41
    On 10/22/17, g00r00 pondered and said...

    The issue is that when MUTIL [MergeNodeLists] stanza is called to mer several nodelists. The corrosponding output in nodelist.txt in the da directory has some additional artifacts introduced in the file.

    Can you give me those specific nodelists so I can try to reproduce the exact issue here?

    No, as time has moved on sadly and I don't retain old nodelists, just the current copy - sorry.


    Sorry I know this is a very late reply and you probably won't still have that data to supply but I thought I'd ask anyway.

    It has been a while (but we're all busy with that thing called real life :)) but in checking my RPi I can see the same artifact appearing today (23 Oct 2017) as it was being reported prior.

    It now shows as an additional control code (or similar) on the final line of
    my nodelist.txt file in the mystic/data directory. Now I have set up a NET3
    it comes up on the final line after all NET3 nodes.

    At the time of this reply the nodelist was FSXNET.300 compressed as FSXNET.Z00 and I observed this behaviour on a RPi running Mystic 1.12 A35

    Best, Paul

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)