Download requests made in bulk failing
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 22/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- node.js, typescript
- 領域
- api
研究方向
No files or tests are named. Start by reproducing the bulk download flow with the Graph API, Fetch, and Node.js at the reported request sizes, then examine the failed requests and whether retries occur. Done requires an identified cause and a verified resolution for intermittent failures, but the issue does not define an expected fix.
由索引模型根據 Issue 內容生成。
描述
Not sure if this is a code related issue, or a network issue. or node related issue. It is hard to pinpoint any root cause as the data received is variable and inconsistent. When requesting downloads in bulk from the Graph API using Fetch and node JS there appears to be an intermittent problem.
At first it was assumed that node and fetch were struggling with the number of requests being made for example we would run an API request to gather info on 1000 files and for each file request a download using the methods provided by the SDK.
What was initially discovered was that when 2000+ files were requested multiple downloads would fail. For example, only 700 of these files would land on disk. In circumstances where downloads were failing there appear to have been no retry attempts.
The flows were checked for event loop lag and the CPU for excessive usage. Neither were apparent as issues. What was indicated in a error response was that fetch was just failing. It was not receiving a response.
A timer was added to create a space between individual requests, this worked and did mediate well. However, it was also apparent that download requests were failing when smaller amounts of files were requested, for example between 400 and 500. It is conceivable that this should not be a problem for an API to manage.
I am just wondering if other SDK/Graph users have encountered this issue.
- 主要語言
- TypeScript
- 星號
- 836
- 分支
- 240
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoftgraph/msgraph-sdk-javascript 的其他 Issue
-
status:waiting-for-triage
難度 1/5 1 小時以內 新手友好度 62/100
-
Is anyone here?未關閉
難度 4/5 3-5 天 新手友好度 25/100
microsoftgraph/msgraph-sdk-javascript#2005 · 1 個 reaction ·
-
status:waiting-for-triage
難度 5/5 一週以上 新手友好度 42/100
-
status:waiting-for-triage type:bug
難度 3/5 1-2 天 新手友好度 48/100
microsoftgraph/msgraph-sdk-javascript#1999 · 2 則留言 · 1 個 reaction ·
-
status:waiting-for-triage type:bug
難度 4/5 3-5 天 新手友好度 45/100
查看 microsoftgraph/msgraph-sdk-javascript 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 85/100
wardian-app/Wardian#1603 ·
維護者通常 1 天內回覆
-
Sign the pledge未關閉
難度 1/5 1 小時以內 新手友好度 85/100
input-output-hk/devx-updates#168 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
agent-ready area: config area: skills type: chore upstream: brain-kit
難度 1/5 1 小時以內 新手友好度 95/100
-
dev experience frontend good first issue
難度 2/5 1-3 小時 新手友好度 78/100
cuttle-cards/cuttle#1403 ·
維護者通常 1 天內回覆