Extension startup fails on large session histories
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 70/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
- 領域
- cli
研究方向
從 handleSessionResumeCore() 開始，追蹤 replayEvents: false 如何經過 initializeSession() 傳遞至 seamHost.initializeSession()。確認在未要求歷史重播時，擴充功能附加路徑不再序列化完整的事件歷史記錄，並使用序列化歷史記錄超過 V8 字串限制的工作階段重現問題。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
Extensions fail to load in a long-running session when the serialized event history exceeds V8's maximum string length. Each affected extension imports successfully, but its joinSession() call fails:
[extension-bootstrap] importing extension: <path>
[extension-bootstrap] Failed to load extension: Error: Request session.resume failed with message: Invalid string length
The failure affects multiple locally configured extensions. In one session, two extensions failed identically. That session's events.jsonl was 1,664,072,585 bytes. Both extensions loaded successfully in smaller sessions using the same installation. The largest session log with a successful extension startup was 97,568,545 bytes. These file sizes do not establish the exact threshold on the serialized event array.
The packaged 1.0.82 bundle shows this call path:
handleSessionResumeCore()handles the extension'ssession.resumerequest and callsinitializeSession()withreplayEvents: false.- The host initialization path ignores that flag and passes
session.getEvents()toseamHost.initializeSession(). seamHost.initializeSession()callsJSON.stringify(events).- V8 throws
Invalid string lengthbecause the result would exceed its maximum string length of 536,870,888 code units.
handleSessionResumeCore() requests no historical replay. Respecting replayEvents: false throughout the initialization path would avoid serializing the event array during extension attachment.
Affected version
GitHub Copilot CLI 1.0.82
Steps to reproduce the behavior
- Configure an extension whose entry point calls
joinSession(). - Open or resume a session whose serialized event history exceeds V8's maximum string length.
- Start or reload the extension.
- Inspect the extension log.
The session.resume request fails with Invalid string length. The extension process then exits before reporting ready.
Expected behavior
Extension startup should not depend on the total size of the session history. joinSession() should complete without materializing unrequested historical events as a single JavaScript string.
Additional context
Environment: Linux x86_64.
#4325 reported the same engine limit for CLI session resume and was closed as completed. Extension attachment still fails.
#4670 tracks stale registrations and hanging tool calls after a startup failure. Reproducing it surfaced this attachment failure, which #4670 records as a separate defect.
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 17 小時 6 分鐘
- 30 天內合併 PR
- 5
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/copilot-cli 的其他 Issue
-
area:sessions
難度 2/5 1-3 小時 新手友好度 72/100
github/copilot-cli#4996 ·
維護者通常 1 天內回覆
-
triage
難度 1/5 1 小時以內 新手友好度 88/100
github/copilot-cli#4963 · 1 則留言 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
github/copilot-cli#4932 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-cli#4909 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 76/100
github/copilot-cli#4906 ·
維護者通常 1 天內回覆
查看 github/copilot-cli 的全部 Issue
相似的 Issue
-
review-drift
難度 2/5 1-3 小時 新手友好度 78/100
oxidecomputer/hansei#14 ·
-
bug
難度 2/5 1-3 小時 新手友好度 75/100
-
omarchy-menu-keybindings lua bind scan spins at 100% CPU when user config iterates a mocked hl API未關閉
難度 2/5 1-3 小時 新手友好度 82/100
omacom/omarchy#14302 · 1 則留言 ·
維護者通常 1 天內回覆
-
Link Checker Report可能已有人在做 @keraron 今天認領。 未關閉automated issue report
難度 2/5 1-3 小時 新手友好度 68/100
a2aproject/A2A#2297 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 88/100
mattpocock/skills#1165 ·