ratatoskr/persistent-memory.d/2026-07-15-re-sub-re-subn-interprets-backslash-escapes-i.md at main

Files

T

vh ff1f9ca1e8 memory: /snapshot — #368 silo test passed; two-tier migration; stores scrubbed

- #368 (user,character) memory silo test DONE + PASSED live (WT b127):
  write-side conjunctive {end_user,agent_self} scoping + read-side cross-
  character isolation both proven end-to-end; betty (throwaway) deleted,
  Sindra intact. Full record in persistent-memory.d/2026-07-18-368-silo-
  test-passed.md. Retired the stale "silo test in progress" in-flight blocks.
- Two-tier migration: split 152 over-threshold dated entries into
  persistent-memory.d/ detail files, leaving one-line pointers in the index
  (startup load ~196KB -> ~53KB; bodies now load on demand).
- Tier-3 stores scrubbed clean (memory 0 / affect 0, provider restarted
  empty); persistent-memory + detail file updated to reflect the scrub.

2026-07-17 21:39:18 -07:00

465 B

Raw Permalink Blame History

[2026-07-15] re.sub/re.subn INTERPRETS backslash-escapes in the REPLACEMENT string — a json.dumps'd value (escaped \n) fed as the replacement leaked REAL newlines into a source file (broke first_message.py with an unterminated-string SyntaxError). Fix: use a FUNCTION replacement (pat.subn(lambda m: new_block, src)) or str.replace — the callable form bypasses escape processing. json.dumps itself escapes correctly; re.sub was the culprit.

465 B Raw Permalink Blame History

465 B

Raw Permalink Blame History