fix: normalize deepgram audio upload bytes
This commit is contained in:
@@ -42,6 +42,7 @@ Docs: https://docs.clawd.bot
|
|||||||
- Messages: refresh live directory cache results when resolving targets.
|
- Messages: refresh live directory cache results when resolving targets.
|
||||||
- Messages: mirror delivered outbound text/media into session transcripts. (#1031) — thanks @TSavo.
|
- Messages: mirror delivered outbound text/media into session transcripts. (#1031) — thanks @TSavo.
|
||||||
- Messages: avoid redundant sender envelopes for iMessage + Signal group chats. (#1080) — thanks @tyler6204.
|
- Messages: avoid redundant sender envelopes for iMessage + Signal group chats. (#1080) — thanks @tyler6204.
|
||||||
|
- Media: normalize Deepgram audio upload bytes for fetch compatibility.
|
||||||
- Cron: isolated cron jobs now start a fresh session id on every run to prevent context buildup.
|
- Cron: isolated cron jobs now start a fresh session id on every run to prevent context buildup.
|
||||||
- Docs: add `/help` hub, Node/npm PATH guide, and expand directory CLI docs.
|
- Docs: add `/help` hub, Node/npm PATH guide, and expand directory CLI docs.
|
||||||
- Config: support env var substitution in config values. (#1044) — thanks @sebslight.
|
- Config: support env var substitution in config values. (#1044) — thanks @sebslight.
|
||||||
|
|||||||
@@ -44,12 +44,13 @@ export async function transcribeDeepgramAudio(
|
|||||||
headers.set("content-type", params.mime ?? "application/octet-stream");
|
headers.set("content-type", params.mime ?? "application/octet-stream");
|
||||||
}
|
}
|
||||||
|
|
||||||
|
const body = new Uint8Array(params.buffer);
|
||||||
const res = await fetchWithTimeout(
|
const res = await fetchWithTimeout(
|
||||||
url.toString(),
|
url.toString(),
|
||||||
{
|
{
|
||||||
method: "POST",
|
method: "POST",
|
||||||
headers,
|
headers,
|
||||||
body: params.buffer,
|
body,
|
||||||
},
|
},
|
||||||
params.timeoutMs,
|
params.timeoutMs,
|
||||||
fetchFn,
|
fetchFn,
|
||||||
|
|||||||
Reference in New Issue
Block a user