Under the hood
Useful1 Signal3
Per-host lazy caches tripled from sixteen to fifty-one, so parallel sessions stay separate.
What's wrong with this entry?
Anonymous. No account, no email.
What
The holder that returns one instance per host, created on first use, went from 16 construction sites in v2.1.231 to 51 here. Two sessions or SDK instances sharing a process no longer share these caches.
Details
- Newly host-scoped: the memory-extraction registry, whose extractor and drainer callbacks are installed per host and drained against a 60000 ms timeout, and an IDE-state holder.
Evidence
P8e = Symbol("ide-not-yet-computed");
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state