AA
M
multipart/form-data - applies to both the Upload Module & script content endpoints. I know other folks are using this in prod but wasnāt sure if we had formally published it.
AAAMAM
K--no-bundle which is basically what you're doing with the API, and allows 'proper' dynamic imports
SSSSELECT * FROM content WHERE json_extract(data, '$.status') = 1SSS
L
__D1_BETA__D1_DB rather than D1_DB that i have specified as the binding in the settings. what could be causing this?L3.4.0 rather than 3.5.1?
CCLS
CS
order by id desc?CS'SELECT * FROM content WHERE json_extract(data, "$.s") IN (0,1) AND json_extract(data, "$.t") IN (0) ORDER BY id DESC LIMIT 10 OFFSET 10' and it worked.order by end of the query, it does not work. Anyways, thanks again.L__D1_BETA_ is being added as a prefix in the environment, but not binding named DB__D1_BETA_DB, but it tells me that there is no function prepare on it.DB variable is hanging on the env that i can call prepare on. any ideas?
M
Cwrangler d1 backup create <db> throws Experimental DBs do not support backups yet
I--persist-to=./path-to-persist-db is not working as expected.M
M
HMM
M
REAL value
M
FMMFMFMFM
N
wrangler dev:Nwrangler.tomlwrangler deploywrangler dev 
multipart/form-data--no-bundleSELECT * FROM content WHERE json_extract(data, '$.status') = 1__D1_BETA__D1_DBD1_DB3.4.03.5.1order by id desc'SELECT * FROM content WHERE json_extract(data, "$.s") IN (0,1) AND json_extract(data, "$.t") IN (0) ORDER BY id DESC LIMIT 10 OFFSET 10'order by__D1_BETA_DBDBbinding name: DB
env contains: __D1_BETA_DB__D1_BETA_DBpreparewrangler d1 backup create <db>Experimental DBs do not support backups yet--persist-to=./path-to-persist-dbREALwrangler devwrangler devā Starting local server...
workerd/server/workerd-api.c++:615: error: wrapped binding module can't be resolved (internal modules only); moduleName = cloudflare-internal:d1-api
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:275: error: e = workerd/server/workerd-api.c++:635: failed: expected !value.IsEmpty(); global did not produce v8::Value
stack: 104c8d3cf 104f000cf 104c55d6f 104c5ad4f 104c5d717 104c5c397 104c4fe87 104c4fc23 104c4fa8f 104c4fa77 106562367 1065625c3 106560d1b 106560aeb 104c441ab 1a8577f27; sentryErrorContext = jsgInternalError
service core:user:<MY_PROJECT_NAME>: Uncaught Error: internal error
ā [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.[[d1_databases]]
binding = "DB" # i.e. available in your Worker on env.DB
database_name = "REDACTED"
database_id = "REDACTED"