Blender add-on: pass CultMeshGrantAllWrites() to its served node #4
Loading…
Reference in a new issue
No description provided.
Delete branch "libby/blender-grant-peer-writes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CultLib PR GameCult/CultLib#33 makes
cultmesh_pyrefuse peer puts/deletes unless awrite_authoritygrants them. This add-on's clients put command intents to its served node, sostart_servernow passeswrite_authority=CultMeshGrantAllWrites()when the loadedcultmesh_pyhas it (older cultmesh_py already accepts all writes and gets no argument).Access rules (for the reviewer): this preserves current behaviour and adds no new access. Peer writes remain open to any connected peer when
require_tokenis off (loopback-only unless the non-loopback box is ticked); withrequire_tokenon,server_guardstill refuses any put/delete without the session token before the base class sees it, so the grant never widens what the token guard admits. Not merging unreviewed.Tests (headless, no Blender):
CULTLIB_PACKAGES=<CultLib>/packages python -m unittest discover -s surfaces/blender/tests. Newtest_a_peer_put_is_accepted_over_tcp_because_the_target_grants_peer_writes. With the CultLib #33 packages: 67 OK (3/3). Without this change against #33: 4 tests fail (this one plus the three token/shard-log tests), proving the reliance. Against CultLib main (no gate): OK (2/2), so the change is compatible both ways. Blender itself is not installed on this host, sotests/live/headless_smoke.pywas not run.Merge order: CultLib#33, then this.
🤖 Generated with Claude Code