1. Forum
  2. Fidonet
  3. SYNC SYSOPS

  • Issue with system.uptime

    From Craig Hendricks@1:103/705 to GitLab issue in main/sbbs on Fri Apr 3 12:03:18 2026
    open https://gitlab.synchro.net/main/sbbs/-/issues/1109

    The system.uptime JavaScript variable is giving unexpected results in current builds.

    Given this line:
    ```
    print("This BBS has been up since " + system.timestr(system.uptime));
    ```

    In b3cec4b69, result is the current date/time:
    ```
    This BBS has been up since Fri Apr 03 2026 02:08 pm
    ```

    In dc7a17727, result is instead:
    ```
    This BBS has been up since Wed Dec 31 1969 08:02 pm
    ```

    Chatted with nelgin and Deuce in IRC; they suspect possibly related to #1093. --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Phillip Taylor@1:103/705 to GitLab note in main/sbbs on Sat Apr 4 05:07:07 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1109#note_8746

    The best thing to do is to add the information to your bulletins. That would be quick fix.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Craig Hendricks@1:103/705 to GitLab note in main/sbbs on Sat Apr 4 05:15:41 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1109#note_8748

    No, the best thing to do is report the issue to the devs so the problem can be fixed for others who may be using system.uptime in their scripts.

    I already restored my BBS to a previous build where it works as expected, so my issue is "fixed" for now.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)