Bob

A bit of an old issue, but i'd say they've implemented this now, called X-Timeout

I've mostly figured this out now, and its actually still accurate still, however it would be greatly improved by suggested that caching also needs to be _enabled_ in CodeBuild. ie:...

> Are there any plans to fix the bug where disabling langsmith by environment variable does not work? Embedding tracing_context into code for disabling is not neat. For the record...

I think i'm a victim of this too! My lamba logs: ``` app-logs | 2024-10-09T03:02:44 {"timestamp":"2024-10-09T03:02:44.451Z","level":"ERROR","message":{"errorType":"Error","errorMessage":"Missing tiktoken_bg.wasm","stackTrace":["Error: Missing tiktoken_bg.wasm"," at node_modules/.pnpm/[email protected]/node_modules/tiktoken/tiktoken.cjs (/var/task/index.js:137027:13)"," at __require2 (/var/task/index.js:18:53)"," at node_modules/.pnpm/@[email protected]_@[email protected]_@[email protected]_js-tiktoken@1._d65gjdt6k6tmj5pmt5qhv3yqf4/node_modules/@llamaindex/env/dist/tokenizers/node.js (/var/task/index.js:137043:32)"," at __init...

Just a note; i was excited by @himself65's merge. I'm now getting this in my env on 0.7.7 during my bundle/synth phase: ``` ✘ [ERROR] No matching export in "node_modules/.pnpm/@[email protected]_@[email protected]_@[email protected]_gpt-tokenizer@_knm3gj4fyseqd4vsl5w3q7owja/node_modules/@llamaindex/env/dist/index.js"...

> @mobob you can create a table with 5 GSIs, you just can't add 4 GSIs to a table that already has one, in one go. Utter nonsense Right -...

Thank you for this @dev-embedthis ! The only option out of your suggestion that could be useful is the use of maxPages, but if as you say it defaults to...

Stumbled across this and might be experiencing similar issues; i just switched over from native OpenAI calls to Vercel AI and am experiencing... lack of reliability with Telemetry. My setup...

Hey @zirkelc ! So i gave that a try and i don't see exactly what you are... it was a relatively quick hack so it's possible the shutdown is happening...

FWIW i've had these exact same smithy issues before, and I always solve it by upgrading and aligning all my aws-sdk package version numbers (including non-dynamo related packages). Not always...