summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-node/src
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-09-06 17:58:27 +0200
committerChristophe Besson <cbesson@gmail.com>2026-09-06 17:58:27 +0200
commit4e6d6573003b06dd58268602d50a98988d4ce3d0 (patch)
tree70f31e0e7f069a8bf34bf5dae3bc902ce0e8e3ee /packages/meshbay-node/src
parentea56b8c79538323875c00db2e7006b255f7cd494 (diff)
downloadmeshbay-4e6d6573003b06dd58268602d50a98988d4ce3d0.tar.gz
test(node): the backslash-path test modelled the wrong platform
It asserted `Path(win_dir).as_posix() == "C:/Users/alice/Media"`, which is only true where `Path` is a `WindowsPath`. On every other machine a backslash is an ordinary filename character, `as_posix()` converts nothing, and the test failed against correct code — so it has never passed on this suite's usual host, and never guarded anything there. `PureWindowsPath` names the flavour and makes it the same assertion on all three platforms. The round trip also only ever proved that `as_posix()` produces a parseable string, never that the config writer calls it — which is the defect, and one no Linux machine can reproduce: the file is written, parsed and served correctly here and fails on the operator's Windows box. A second test reads ops.py for every f-string landing on the right of a TOML `path =` and requires `as_posix()` in it. Weak evidence, and the only kind available for a platform the suite does not run on; checked to fail with the call removed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011pvMdvLBG92jyhvD5pD6us
Diffstat (limited to 'packages/meshbay-node/src')
0 files changed, 0 insertions, 0 deletions