meshbay.git/packages/meshbay-node, branch 0.21

chore: bump version to 0.21.0

2026-10-17T21:15:02Z

Co-Authored-By: Claude Opus 5.5

fix(node): the answer log names its host addresses

2026-10-17T16:19:15Z

aiortc ends a host candidate line at `typ host`, so the match on " typ host " found none and logged `host: none` for every answer. Co-Authored-By: Claude Opus 5.5

fix(node): datagrams straight through the socket on Windows' event loop

2026-10-16T10:28:25Z

The ProactorEventLoop's datagram transport keeps one overlapped operation per direction and starts the next from the previous one's completion, on a later turn of the loop: one datagram sent and one received per socket and per turn, however many wait. The busier the node, the slower every connection, with cores to spare. Measured on loopback with the loop busy 0.5 ms a turn: 1,928 datagrams sent a second and 1,954 received, 87 % of the rest dropped by the kernel. A browser's download from a node holding its connections ran at 9 MB/s, the node at 45 % of a core, SCTP round trip 745 ms. Now a datagram goes out with a non-blocking sendto when nothing is queued, and a completed read is followed by whatever the socket holds before the next one is posted. Two-core machine, 400 MB: CLI download 27 -> 33 MB/s, upload 18 -> 22, browser over eight connections 9-14 -> 17-19. Co-Authored-By: Claude Opus 5.5

Merge branch 'main' of meshbay.org:meshbay

2026-10-16T09:11:25Z

feat(node): connection processes on by default, one per core up to four

2026-10-16T08:41:17Z

At 1 no process starts and every lane of a download lands on the node's one core. The Node page also sent every setting on each Save, pinning untouched ones at the day's default; it sends only what changed. Co-Authored-By: Claude Opus 5.5

perf: linear SCTP reassembly, one SACK every second packet, 4 MB buffer in the CLI

2026-10-16T08:41:17Z

aiortc walked a message's fragments after each one arrived (n^2/2 steps for a 1 MiB chunk) and acknowledged every packet. Measured on loopback, 400 MB to the CLI: 19 MB/s before, 39 after (49 by the node's count); uploads from the CLI 25 -> 29 MB/s. Co-Authored-By: Claude Opus 5.5

fix(packaging): the command-line client's Store alias on an application of its own

2026-10-15T16:12:09Z

An Application declares one windows.appExecutionAlias extension, and the app's is meshbay-node.exe; the second one added for meshbay-cli.exe made makeappx refuse the package ("must only be declared once") at the very end of the Store build. The client is now an Application of its own, out of the Start menu, carrying its alias. Built: MeshBay-0.20.0.appx with both aliases. Co-Authored-By: Claude Opus 5.5

chore: bump version to 0.20.0

2026-10-15T15:45:41Z

Co-Authored-By: Claude Opus 5.5

build: ignore the Windows build's work directories; a Linux mode check off Windows

2026-10-15T15:45:41Z

packages/meshbay-client/build/_pip-audit (and its siblings) is made by the Windows build and was untracked noise. test_packaging_default_env checked a POSIX file mode that Git's bash on Windows cannot set. Co-Authored-By: Claude Opus 5.5

fix(packaging): setup ends a command-line client run from its install

2026-10-15T15:45:41Z

A `meshbay-cli chat --follow` left open holds node-runtime's DLLs, so the previous version's uninstaller failed ("Failed to uninstall old application files"), a silent update included, and left the node it had stopped not running. stop-node.ps1 now ends a meshbay-cli.exe run from this install (-InstallDir, setup's $INSTDIR), and no other copy. Found through CIM, not Get-Process: setup runs the 32-bit PowerShell, which reads no path for a 64-bit process, and the first version of the stop matched nothing. The test runs the script in that PowerShell. Checked live: an update over a running follower now ends it, replaces every file and restarts the node. Co-Authored-By: Claude Opus 5.5