https://gitlab.synchro.net/main/sbbs/-/commit/65bde885de939d6b1157382e
Modified Files:
src/sbbs3/jsexec.c
Log Message:
More verbose help output for -L option

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/29001ba126bfd344c1f9ad63
Modified Files:
src/sbbs3/jsexec.c
Log Message:
This should allow it to link as a console program.

---
ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/20da5318bafa58eb3ead19e2
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Fix (harmless) memory leak reported by ASan when running 'jsexec -?'

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/cd997ea347ee9db7c5f3e474
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Resource cleanup on exit (when no module specified)

Eliminates a SANITIZE build error

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/40995ce1868fdb8cdbacf2a6
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Insure the exec_dir is *always* prepped (fix for Windows upgrade to v3.20)

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.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/7b932f63e4f1d4275e55dfbf
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Only create/use a single run-time for use in JSexec, even when re-runnning

The '-l' (loop) option would cause the JS runtime to be destroyed and
recreated for each new execution of the script, which resulted in memory
leaks in Windows builds (see issue #672 for details). So instead, just
use a single JS runtime here when the -l option is used to prevent that
from happening, though truth be told, that's likely not a normal/common occurrence. Other apparent JS-related memory leaks (e.g. in the web
server) appear to be of a common concern.

Likely upgrading to a modern libmozjs would also fix this issue, but
we're far short of being able to do that right now.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/b53254b6bcc9d02aae63da2e
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Resolve full path to specified ctrl directory, before chdir

If a relative path to the ctrl directory is specified on the command-line
or in the SBBSCTRL environment variable, the loading of ctrl/*.ini would
fail after the changing of the working directory.

We should probably get replace all use of FULLPATH with _fullpath someday,
but for now, I just went with majority-rule.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/7d3b61d7f59fcdf32e739baf
Modified Files:
src/sbbs3/jsexec.c
Log Message:
PATH_MAX (not an MSVC thing) -> MAX_PATH

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/97fb3f1f463adc057fc05ea8
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Make Windows hack Windows-only

We need _CIOLIB_main on macOS... at least until the curses stuff works.

---
ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/1e48f1252859924638b52e96
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Don't use the non-standard third parameter to main for enivronment

Use the standard `extern char **environ' instead.
Fixes an issue with macOS.

Also, check that env is not NULL in js_init.

---
ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/ebe52737cd48d45a843d12ea
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Temporary debug to find out where/why jsexec is hanging during mac mini m4 CI test

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/4ce915370298c9c4912a4d40
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Add an fflsuh() for temp debug spew

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/e8a981d77522a6ecd880e741
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Revert "Add an fflsuh() for temp debug spew"

This reverts commit 4ce915370298c9c4912a4d4095852854a0726225.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/0d8ef460eb35c72548a51310
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Revert "Temporary debug to find out where/why jsexec is hanging during mac mini m4 CI test"

This reverts commit ebe52737cd48d45a843d12eaa7909551f491cc36.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/0e24a32ba6985a26dad9655f
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Increase formatted log/console output buffers from 1K to 8K

... make them more useful (e.g. when the result of script is a big string).

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/2e2bcb707a2f03ea5e95b78e
Modified Files:
src/sbbs3/jsexec.c
Log Message:
MethodJIT crashes on OpenBSD

Disable it in jsdoor

---
ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/8ca065ccc2ac94cbf2807da0
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Check/read the passed module path/name section in jsexec.ini first

... before the more ambiguous base filename check.

e.g. if you run 'jsexec /path/to/test.js' and get separate set of settings
from running 'jsexec test.js' depending on which sections you have added to your jsexec.ini file.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/d55b899a806bae8f537421b2
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Fix misalignment (by uncrustify?)

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net