{"version":"2.1.248","anchor":"memory-backend-rejects-an-undecided-host-file-setting","canonical_anchor":"memory-backend-rejects-an-undecided-host-file-setting","heading":"Memory backend rejects an undecided host-file setting","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/memory-backend-rejects-an-undecided-host-file-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Memory backend rejects an undecided host-file setting\n\nThe in-memory backend refuses to build unless host-file spaces are explicitly decided.\n\n**What**\n\nBuilding 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.\n\n**Evidence**\n\n`tryCreateMemoryV5Backend: the workspace and userNamed spaces are served or refused, never attested`\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}