- Jun 03, 2023
-
-
Rob Swindell authored
Keyop reported an issue via irc whereby a user that failed to download a file would leave the node "hung" in "downloading via telnet" node status even though the user had long since disconnected and the log reflected that the terminal server was aware of this: term Node 4 <user> sexyz: !1152 zmodem_recv_raw TIMEOUT (10 seconds) term Node 4 <user> sexyz: !zmodem_recv_header TIMEOUT term Node 4 <user> external Timeout waiting for output buffer to empty <minutes later> term Node 4 connection reset by peer on send term Node 4 !ERROR 32 sending on socket 102 term Node 4 !ERROR 32 sending on socket 102 term Node 4 !ERROR 32 sending on socket 102 term Node 4 !ERROR 32 sending on socket 102 term Node 4 !ERROR 32 sending on socket 102 term Node 4 disconnected term Node 4 !ERROR 32 sending on socket 102 and term Node 3 <user> sexyz: !1152 zmodem_recv_raw TIMEOUT (10 seconds) term Node 3 <user> sexyz: !zmodem_recv_header TIMEOUT term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !Receive timeout (1 seconds) term Node 3 <user> sexyz: !1152 zmodem_recv_raw TIMEOUT (10 seconds) term Node 3 <user> sexyz: !zmodem_recv_header TIMEOUT term Node 3 <user> external Timeout waiting for output buffer to empty <minutes later> term Node 3 connection reset by peer on receive term Node 3 !ERROR 32 sending on socket 96 These nodes were then locked up in call to passthru_socket_activate(false) as reported by gdb, e.g. Looking at passthru_socket_activate(), the deactivation path (called at the end of external() in this case), it was clear that this could be an infinite loop in the case the user had disconnected: do { // Allow time for the passthru_thread to move any pending socket data to the outbuf SLEEP(100); // Before the node_thread starts sending its own data to the outbuf } while(RingBufFull(&outbuf)); These flush/purge loops aren't strictly needed if the user has disconnected, but as can be seen by the above logs, the terminal server may not know that (the socket may not indicate disconnect) before passthru_socket_activate() is called by external(). So... worst case, just do the activation and deactivation buffer flushes and purges for 60 seconds.
-
- Jun 02, 2023
-
-
Deucе authored
On Linux, this changes the program name shown in top.
-
Deucе authored
This allows X11 stuff to work properly.
-
Deucе authored
-
Deucе authored
Actually install the colormap we create. Remove the 48x48 icon. As it happens, ChromeOS completely ignores the X11 icons and instead does some weird magic to drag the icon .png file out of the VM and uses that. Basically, getting the icon to work appears to mean putting some properly named files into magic directores.
-
Deucе authored
USize was wrong, PSize wasn't set, and PBaseSize was set, but flag wasn't.
-
Deucе authored
-
Deucе authored
-
Deucе authored
Also, set both _NET_WM_ICON and WMHint icon pixmap
-
Deucе authored
It seems whatever WM XWayland uses doesn't actually use _NET_WM_ICON like pretty much everything else for the last 30 years does, so we need to go old-school or settle for the default pengion icon, which offends me personally.
-
Deucе authored
-
Deucе authored
The bracketpaste "bit" was set to 0x16, not 0x10 or 16 as intended. Erase line would erase the wrong line if the scrolling region didn't start on line 1.
-
- Jun 01, 2023
-
-
Deucе authored
-
Deucе authored
-
Deucе authored
The sketchiest bit here is removing the uifc -> conio dependency which, since it needs to depend on conio_sdl now means if something is relying on that, it will need an explicity dependency... We'll see what the pipeline says.
-
Deucе authored
-
Deucе authored
-
Deucе authored
-
Deucе authored
Maybe, who knows?
-
Deucе authored
-
Deucе authored
"I can't think of a reason I'd want scfg and echocfg to remain windows (gui) programs" -- Digital Man While I'm here, hack up some SyncTERM vcxproj stuff (which almost certainly doesn't work, but since I can actually test it now, I may as well try)
-
Deucе authored
-
Rob Swindell authored
-
Deucе authored
Also, prevent unreachable and unleavable sectors.
-
Rob Swindell authored
For use with jsexec
-
Rob Swindell authored
... or else any pending published messages aren't sent.
-
Rob Swindell authored
Similar to (mimics) mosquitto_sub
-
Rob Swindell authored
-
Rob Swindell authored
-
- May 31, 2023
-
-
Deucе authored
At the same time, add BD, BE, PE, and PS to the terminfo entry. Note that it seems this is "normally" detected by seeing if $TERM contains "xterm" which shouldn't work with SyncTERM (which is wildly incompatible), but the terminfo source file here: https://invisible-island.net/ncurses/terminfo.ti.html Gives us hope in the form of this comment: https://invisible-island.net/xterm/xterm-paste64.html Bracketed paste was introduced by xterm patch #203 in May 2005, as part of a larger feature for manipulating the clipboard selection. Few terminals aside from xterm fully implement the clipboard feature, but several copy this detail. The names for the extended capabilities here were introduced by vim in January 2017, but used internally. In 2023, vim patch 9.0.1117 is needed to work with this change. That is to say that it likely won't work on anyone's system today (except maybe Cyan's), but it may magically start working in the future... assuming tic supports these capnames. No real clue there since there's absolutely no termcap support, and I use FreeBSD.
-
Deucе authored
Previously, delete lines would erase the line above the current one. This was visible in vim which makes extensive use of delete line to scroll.
-
Deucе authored
Some shell pwd implementations default to the "Logical" PWD, which can contain symlinks. The POSIX standard for /bin/pwd is to return the "Physical" PWD with all symlinks resolved. Some shells don't support the -P option the the built-in pwd, so we don't want to reply on that. For some reason, we're redefining the PWD env variable which should by the phyical path, but I'm not really interested in tracking down all the windy history for this. Basically, this bit me once, and now it's fixed.
-
Deucе authored
In theory, this will allow higher quality scaling in GDI mode if the graphics driver supports it... It doesn't look like the drive used for VirtualBox does though, so I can't tell if it does anything or not.
-
Deucе authored
Use the default visual and depth instead of "best" Use Xrender for sclaing when library is available and server supports it Set VisualIsRGB8 when possible
-
Rob Swindell authored
Don't require Git when building from tarball
-
Rob Swindell authored
Clear console abort flag after prompting for destination user
-
Rob Swindell authored
-
Rob Swindell authored
e.g. when running filelist.js as a timed event, you can't redirect stdout (without running via jsexec), so let's support specifying an output filename with an option (-out=filename).
-
Rob Swindell authored
It's unclear whether trailing whitespace is supposed to be significant or not (FidoNet specs don't say), but I don't see any reason why "John Doe" and "John Doe " should be considered unique senders or recipients. Remove any trailing whitespace from message subjects too. This change makes the trailing whitespace truncation in SMB hash functions unnecessary (at least for SBBSecho-imported messages), but most (all?) other message transports don't allow for this nonsense in the first place.
-
- May 30, 2023
-
-
Rob Swindell authored
Log a warning message when either the "local" or "in-transit" flag has been stripped from ("Sanitized") imported packed-messages. Keyop reported a chksmb warning on a FidoNet message that contained the 'in-transit' attribute: <Keyop> Message flagged as 'In Transit' (?): 1 <Keyop> fidonet_fidosoft Message Base has Errors! The message in question appears just to be a corrupted echomail msg coming from HPT: Sender '56:43 ' To Tommi Koivula Subject test X-FTN-AREA FIDOSOFT.HUSKY X-FTN-TID hpt/os2-wc 1.9.0-cur 2021-03-14 SBBSecho didn't use to convert/import the "in-transit" flag on imported netmail or echomail messages, ... until commit 446ab0ef, which was needed to support the TickFix robot. So now, let's just sanitize the packed-message attributes a little sooner in the import process and log a warning when such sanitization has taken place.
-