1. Forum
  2. Fidonet
  3. SYNC SYSOPS

  • "logonlist.js -l" reports last callers out of order

    From Nick Boel@1:103/705 to GitLab issue in main/sbbs on Sun Jun 9 05:27:03 2024
    open https://gitlab.synchro.net/main/sbbs/-/issues/761

    Looks like "?logonlist -l" reports 'same day' calls in ascending order, while the next day (or previous days) are in a descending order. Would like for it all to be in one order, or even configurable with an option "?logonlist -l -a" for ascending, or "?logonlist -l -d" for descending? See below for screenshot.

    https://pharcyde.org/logonlist.png
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nicholas Boel@1:154/10 to Gamgee on Sun Jun 9 09:15:02 2024
    Hello Gamgee,

    On Sun, Jun 09 2024 13:17:00 -0500, you wrote:

    https://pharcyde.org/logonlist.png

    This looks correct/normal to me. The first sort is by date, and then
    it's sorted by the time of connection on that date, top to bottom.

    As we discussed on IRC, If the date were to go in the same order as the time of connections on the same day, the newest calls would be at the bottom of the list. Currently, they are not sorted in order, *by call*. The "total connections" column on the left side of the screenshot will show you that they are not in order.

    Would just like to see it possibly configurable for ascending, decending, or leave it how it is, is all.

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sun Jun 9 15:47:45 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/761#note_5368

    I'm not seeing this. In all cases, for me, logonlist.js is returning the logons in the same order they are listed in the `data/logon.*jsonl` file (the same order in which they are added to the file, during logon).

    Maybe you're looking at the `data/logon.lst` file instead?
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Nicholas Boel on Sun Jun 9 15:56:27 2024
    Re: "logonlist.js -l" reports last callers out of order
    By: Nicholas Boel to Gamgee on Sun Jun 09 2024 09:15 am

    Hello Gamgee,

    On Sun, Jun 09 2024 13:17:00 -0500, you wrote:

    https://pharcyde.org/logonlist.png

    This looks correct/normal to me. The first sort is by date, and then it's sorted by the time of connection on that date, top to bottom.

    As we discussed on IRC, If the date were to go in the same order as the time of connections on the same day, the newest calls would be at the bottom of the list. Currently, they are not sorted in order, *by call*. The "total connections" column on the left side of the screenshot will show you that they are not in order.

    Would just like to see it possibly configurable for ascending, decending, or leave it how it is, is all.

    As it is now, logonlist.js and the underlying libraries (json_lines.js, logonlist_lib.js) don't "sort" the entries at all - they are always displayed "how it is", in the order the entries are in the file, which is the same order in which they are added to the file during logon (by default, in logon.js).
    --
    digital man (rob)

    Synchronet "Real Fact" #46:
    Synchronet External X/Y/ZMODEM protocol driver (SEXYZ) was introduced in 2005 Norco, CA WX: 76.1øF, 58.0% humidity, 14 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nick Boel@1:103/705 to GitLab note in main/sbbs on Sun Jun 9 17:17:31 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/761#note_5369

    I'm definitely not using data/logon.lst whatsoever (however, that seems to display the last 7 callers in order). I'm using this to display the last callers:

    // Last few callers
    console.aborted=false;
    console.clear(LIGHTGRAY);
    if(options.show_logon_list === true)
    bbs.exec("?logonlist -l");
    if(bbs.node_status != NODE_QUIET && ((system.settings&SYS_SYSSTAT) || !user.is_sysop))
    bbs.mods.logonlist_lib.add();

    .. that is all.

    Maybe this is because you're only looking at the last 4-5 callers? I've been listing 10, and it doesn't look like data/logon.jsonl is even showing that many, so maybe that's why.

    That said, currently I have 5 calls from today, and they are listed in the order as they are in data/logon.jsonl, 34279-34283. Then, the 6th most recent caller is listed as 34275 from yesterday, and then the 7th caller is 34265, from 6/4/24 (which looks like it's listed in logon.0.jsonl, and the 8th caller is 34266, also from 6/4/24 (which looks like it's listed in logon.1.jsonl.

    So that's probably where the problem lies, when it backtracks into older files.

    So I guess I would say try loading a longer list of last callers and you'll see what I mean.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sun Jun 9 17:37:46 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/761#note_5370

    Okay, yeah, I see now: when pulling from previous days to form the last few callers list, they're not in order.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Sun Jun 9 17:51:13 2024
    close https://gitlab.synchro.net/main/sbbs/-/issues/761
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Accession@1:103/705 to Digital Man on Sun Jun 9 19:22:16 2024
    Hello Digital,

    On Sun, Jun 09 2024 22:56:26 -0500, you wrote:

    Would just like to see it possibly configurable for ascending, decending, or
    leave it how it is, is all.

    As it is now, logonlist.js and the underlying libraries (json_lines.js, logonlist_lib.js) don't "sort" the entries at all - they are always displayed "how it is", in the order the entries are in the file, which
    is the same order in which they are added to the file during logon (by default, in logon.js).

    In that case, is there a setting somewhere to log 10 entries in logon.jsonl so they show up in order? It seems it's only logging 5, and then going back to older files, ie: logon.0.jsonl, logon.1.jsonl, etc. which is what seems to be putting them out of order (since it seems as though every list is ascending).

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    # Origin: _thePharcyde distribution system (Wisconsin) (723:1/1)
    ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)