Hey, is it possible to trigger AutoRAG to re-index from the API? Couldn't find any way to do this?
Hey, is it possible to trigger AutoRAG to re-index from the API? Couldn't find any way to do this?
VECTOR_QUERY_ERROR (code = 40006): invalid query vector, expected 768 dimensions, and got 0 dimensionsconsole.log(“Vector length:”, queryVectorRaw.length); // 768console.log(“typeof vector[0]:”, typeof queryVectorRaw[0]); // “number”console.log(“Array.isArray:”, Array.isArray(queryVectorRaw)); // true
env and it's completely missing, and running into errors with it. Even when I use --experimental-vectorize-bind-to-prod it's failing (definitely have the right binding name etc)[worker name] has access to the following bindings:. But when I try to use it in the code and when I dump env, it's not therevite dev but not when running wrangler dev (I need wrangler dev because I am running two workers at once)auxiliaryWorkers config through vite instead. Pretty broken with wrangler dev still but at least I'm unblocked. Thanks for coming to my TED talk everyoneQueried Vector Dimensions for that request? I have multiple tenants with different sets of vector, so looking for an efficient way to manage these. Creating one index per tenant would work, but it seems to complicate the bindings a bit.VECTOR_QUERY_ERROR (code = 40006): invalid query vector, expected 768 dimensions, and got 0 dimensionsconsole.log(“Vector length:”, queryVectorRaw.length); // 768console.log(“typeof vector[0]:”, typeof queryVectorRaw[0]); // “number”console.log(“Array.isArray:”, Array.isArray(queryVectorRaw)); // true--experimental-vectorize-bind-to-prod[worker name] has access to the following bindings:vite devauxiliaryWorkersQueried Vector Dimensions