Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

TypeError when Downloading to PDF in Azure App Service: undici failure

未關閉
#1,990 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
azure, node.js, typescript
領域
api, backend, cloud

研究方向

Start with conversionDownloadToPdf and the @microsoft/microsoft-graph-client request using ResponseType.RAW, then compare the local and Azure App Service environments on Node v18.19.1. Inspect the full undici error cause and determine whether ProxyAgent or an officially documented workaround addresses the failure; done means the PDF download works in Azure or the limitation is clearly documented.

由索引模型根據 Issue 內容生成。

描述

Download to PDF Not Working in Azure App Service

I'm running an express app using Node v18.19.1. My endpoint does the following:

  1. Saves a document to a sharepoint folder
  2. Performs the download/convert to pdf
  3. Saves the downloaded pdf to a Mongo db.
  4. Deletes the original file

Steps 1, 2, and 4 use the @microsoft/[email protected] package. This all works locally. However, when I deploy it to my Azure App Services (running Windows and Node v18.19.1), it breaks at step 2 with the following error:

TypeError: fetch failed at node:internal/deps/undici/undici:12625:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

The conversion download method:

const conversionDownloadToPdf = async (fileItemId) => {
    try {
        console.log(chalk.blue(`Attempting to downloaded file (${fileItemId})...`));

        const response = await client.api(`drives/${process.env.DRIVE_ID}/items/${fileItemId}/content?format=pdf`)
            .responseType(ResponseType.RAW) // ensure raw stream
            .get();

        const stream = await apiRequest.responseType(ResponseType.RAW).get(); // BREAKS HERE

        console.log(chalk.blue(`Stream downloaded. Streaming to buffer...`));
      
        return await toBuffer(stream);
    } catch (error) {
        console.error(chalk.red(`Full error details:`));
        console.error(chalk.red(`Message: ${error.message}`));
        console.error(chalk.red(`Status Code: ${error.statusCode}`));
        console.error(chalk.red(`Code: ${error.code}`));
        console.error(chalk.red(`Stack: ${error.stack}`));
        
        // Log the cause if available (undici errors have this)
        if (error.cause)
            console.error(chalk.red(`Cause: ${JSON.stringify(error.cause, null, 2)}`));

        throw error;
    }
}

Do I need to use that ProxyAgent? Do you have official docs on a workaround?

主要語言
TypeScript
星號
834
分支
240
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

microsoftgraph/msgraph-sdk-javascript 的其他 Issue

查看 microsoftgraph/msgraph-sdk-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。