Skip to content
Snippets Groups Projects
  1. Aug 09, 2023
    • Eric Oulashin's avatar
      DD Upload Processor: Scan failure output is now logged to the system log... · dd5d5b56
      Eric Oulashin authored and Rob Swindell's avatar Rob Swindell committed
      DD Upload Processor: Scan failure output is now logged to the system log instead of outputted to the logged-in user
      dd5d5b56
    • Rob Swindell's avatar
      Code indentation change only. · 2a85e911
      Rob Swindell authored
      2a85e911
    • Rob Swindell's avatar
      Insure the exec_dir is *always* prepped (fix for Windows upgrade to v3.20) · e5753faf
      Rob Swindell authored
      A "prepped" means directory means a relative path from the configuration files
      (or default settings) has been converted to a full/absolute path with proper
      slashes for the platform (i.e. backslashes instead of forward-slashes on
      Windows).
      
      JSexec doesn't require that the new v3.20 ctrl/*.ini files exist to run; this
      was necessary to be able to run 'jsexec update -> upgrade_to_v320.js' which
      does the ctrl/*.cnf to .ini file conversion (egg not required to build
      chicken). When JSexec failed to load ctrl/msgs.ini
      (e.g. "!ERROR loading configuration files: 2 (No such file or directory)
      opening /sbbs/ctrl\msgs.ini"), it would continue to run, but not "prep" any
      of the "path" settings (e.g. exec_dir).
      
      The first run of 'jsexec update.js' would fail to run upgrade_to_v320.exe
      (which does the v3.20 user base conversion) and a bunch of other (but not as
      important) update steps because Windows couldn't execute "../exec/*".
      
      Multiple errors would be displayed in this case, but the most important (as
      reported by Ree in #synchronet of irc.synchro.net) was:
        '..' is not recognized as an internal or external command
      
      right after the status output:
        No v3.20 user base found, running ../exec/upgrade_to_v320
      
      Notice the "../exec/" prefix, which is not support by Windows when specifying
      a file path to execute.
      
      A second run of 'jsexec update' would work fine because the new v3.20 .ini
      files would be successfully created after the first run (though the user base
      was not).
      
      This is likely the same issue that MRO reported recently when upgrading a
      Windows SBBS v3.19 install to v3.20 and not having the user base upgraded
      the first time.
      e5753faf
  2. Aug 08, 2023
  3. Aug 07, 2023
  4. Aug 05, 2023
    • Rob Swindell's avatar
      Don't publish "null" node input topic · 599d3222
      Rob Swindell authored
      get_ansi_seq() here can return null, don't pass that value to mqtt.publish()
      which gets converted to a string.
      599d3222
    • Rob Swindell's avatar
      Add character set translation (CP437 <> UTF-8) · 33b73ce3
      Rob Swindell authored
      ... for when your terminal and the node client terminal don't use the same
      character set. Only CP437 and UTF-8 addressed in this commit, not PETSCII
      or plain ASCII.
      
      This was never possible before MQTT.
      33b73ce3
    • Rob Swindell's avatar
      Support for spying via MQTT between nodes · c689cdc7
      Rob Swindell authored
      For read-only spying, the mqtt_spy.js module can be used via jsexec (from an
      OS shell command prompt), similar to mosquitto_sub.
      
      For read-write spying, just use the ;SPY sysop command as before and if MQTT
      is configured/enabled, it'll use MQTT rather than sockets or shared memory
      queues to spy on the target node.
      
      For the first time, you can spy between nodes that are on different servers of
      the same BBS using the ;SPY sysop command.
      
      Passes through ctrl characters (except Ctrl-C), unlike the built-in spy
      function. This could be revisited later or made optional, but it sems to make
      sense to allow Ctrl-Z (e.g. to save a message in fseditor.js) to be passed
      through to the target node.
      c689cdc7
  5. Aug 04, 2023
    • Rob Swindell's avatar
      Don't leave socket open when dial() reports "NO CARRIER" · 948136d1
      Rob Swindell authored
      As reported by Deon on DOVE-net, when the call to socket_recvdone() returns
      true (socket is disconnected and all data has been recv()ed), dial() would
      report "NO CARRIER" but leave the open socket opened, thus preventing any
      subsequent dial attempt ("Can't dial: Already connected" and "ERROR").
      
      Also removed the source file path/name from the debug print statements - don't
      need that noise.
      
      Incremented the version to 0.4
      948136d1
  6. Aug 03, 2023
  7. Jul 31, 2023
  8. Jul 30, 2023
  9. Jul 29, 2023
  10. Jul 26, 2023
  11. Jul 25, 2023
  12. Jul 21, 2023
Loading