Not switched on
Useful1 Signal2
The in-memory backend refuses to build unless host-file spaces are explicitly decided.
Behind the same storage gate as the rest of the memory backend.
What's wrong with this entry?
Anonymous. No account, no email.
What
Building the in-memory backend now throws unless the map saying which host file spaces to serve gives strict true or false for both the workspace and user-named spaces. Neither may be left to an attested or indeterminate value. Sits behind the same gate as the rest of this memory work.
Evidence
tryCreateMemoryV5Backend: the workspace and userNamed spaces are served or refused, never attested
Strings lifted out of the shipped bundle, so the claim above can be checked against them.