Adapt other media types to artifacts service #39
Description
,111,109,105,99,61,92,34,116,114,117,101,92,34,62,60,47,100,105,118,62,92,92,110,32,32,60,47,98,111,100,121,62,92,92,110,60,47,104,116,109,108,62,92,92,110,92,92,110,39,34,125,3,2,123,125,2,0,0,0,0,0,0,0,0,5,"$debug":null}}, "code": undefined, "cause": RuntimeError: Aborted(Cannot enlarge memory arrays to size 17592320 bytes (OOM). Either (1) compile with -sINITIAL_MEMORY=X with X higher than the current value 16973824, (2) compile with -sALLOW_MEMORY_GROWTH which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -sABORTING_MALLOC=0), "note": undefined }
at catch (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/connection.js:29:27)
at file:///root/.cache/deno/npm/registry.npmjs.org/effect/3.15.5/dist/esm/internal/core-effect.js:50:55
at @livestore/common:execSql (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/connection.js:32:12)
at @livestore/common:leader-thread:materializeEvent (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/materialize-event.js:84:20)
at @livestore/common:LeaderSyncProcessor:materializeEventItems (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/LeaderSyncProcessor.js:395:55)
at @livestore/common:LeaderSyncProcessor:boot (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/LeaderSyncProcessor.js:217:20)
at @livestore/common:leader-thread:boot (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/make-leader-thread-layer.js:81:16)
at @livestore/common:leader-thread (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/common/0.3.1/dist/leader-thread/make-leader-thread-layer.js:81:73)
at @livestore/adapter-node:adapter (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/adapter-node/0.3.1/dist/client-session/adapter.js:97:16)
at createStore:makeAdapter (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/livestore/0.3.1/dist/store/create-store.js:69:80)
at createStore (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/livestore/0.3.1/dist/store/create-store.js:107:20)
at createStore (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/livestore/0.3.1/dist/store/create-store.js:30:16) {
[cause]: RuntimeError: Aborted(Cannot enlarge memory arrays to size 17592320 bytes (OOM). Either (1) compile with -sINITIAL_MEMORY=X with X higher than the current value 16973824, (2) compile with -sALLOW_MEMORY_GROWTH which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -sABORTING_MALLOC=0)
at abort (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/wa-sqlite/1.0.5-dev.2/dist/wa-sqlite.node.mjs:528:11)
at abortOnCannotGrowMemory (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/wa-sqlite/1.0.5-dev.2/dist/wa-sqlite.node.mjs:4167:7)
at _emscripten_resize_heap (file:///root/.cache/deno/npm/registry.npmjs.org/@livestore/wa-sqlite/1.0.5-dev.2/dist/wa-sqlite.node.mjs:4173:7)
at <anonymous> (wasm://wasm/0029476a:1:32344)
at <anonymous> (wasm://wasm/0029476a:1:24036)
at <anonymous> (wasm://wasm/0029476a:1:555310)
at <anonymous> (wasm://wasm/0029476a:1:52270)
at <anonymous> (wasm://wasm/0029476a:1:52528)
at <anonymous> (wasm://wasm/0029476a:1:51962)
at <anonymous> (wasm://wasm/0029476a:1:51639)
}
}
spanId: livestore-noop-span-id
traceId: livestore-noop-trace-id
thread: window
debugInstanceId: wj5jXZb9R5
storeId: runtly-74
Sometimes users are going to print out something "too big" and we have to gracefully handle it. When this happens we probably shouldn't accept it on the livestore. The size of this data was about 1 MB (printing a CSV as text on accident).