diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-09-19 01:02:05 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-09-19 01:49:56 +0200 |
| commit | c2c49182e6d4f1f1ef3ed3ba5e8699912f9a27bd (patch) | |
| tree | 026a7e4347d4580ed4914605019db50c5794a49b /packages/meshbay-node/tests/test_chat_is_bounded.py | |
| parent | 345a59fc128e5e4f253c277c8cee69a2b1062a4f (diff) | |
| download | meshbay-c2c49182e6d4f1f1ef3ed3ba5e8699912f9a27bd.tar.gz | |
feat(node): per-file upload ceiling is an operator setting, default 8 GB
Was a 4 GB constant in webrtc_server.py, the same on a small board and on
a machine holding a library. Now max_upload_gb in node.toml, on the Node
page and via `meshbay-node transfers max-size`, read from the transport
context per chunk so a change reaches an upload already running.
MESHBAY_DESIGN.md §6.4; §15.3 records a defect found beside it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'packages/meshbay-node/tests/test_chat_is_bounded.py')
| -rw-r--r-- | packages/meshbay-node/tests/test_chat_is_bounded.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/packages/meshbay-node/tests/test_chat_is_bounded.py b/packages/meshbay-node/tests/test_chat_is_bounded.py index 1af72b4..4e767bc 100644 --- a/packages/meshbay-node/tests/test_chat_is_bounded.py +++ b/packages/meshbay-node/tests/test_chat_is_bounded.py @@ -13,7 +13,7 @@ it in `chat.db` on the operator's disk, where nothing expires it — retention i a manual CLI command (§6.6) — relays it to every other connected member, and has the hub write a notification for every member of the group. Uploads, the other member-supplied write, have carried a filename allowlist, strict chunk -ordering, a no-overwrite rule and a 4 GB cap since C5a. Chat carried nothing: +ordering, a no-overwrite rule and a per-file size cap since C5a. Chat carried nothing: the only ceiling was the DataChannel frame, 64 MB once the handshake is done. One member in a loop filled the operator's disk and saturated everyone else's connection, and the node's own answer to each message was `ack`. |