MoonshotAI / MoonshotAI/kimi-code
kimi web 没有把 wasm 正确汇报为 Content-Type application/wasm 类型
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
你运行的 Kimi Code 版本是？
Kimi Code v0.40.1
你使用的是哪个开放平台/订阅？
kimi.com
你使用的是哪个模型？
No response
你的电脑平台是？
No response
你遇到了什么问题？
没有把 wasm 正确汇报为 Content-Type application/wasm 类型，而是 octet-stream，导致无法流式载入，只能 ArrayBuffer 载入 WASM
复现步骤？
直接打开浏览器查看报错信息
期望的行为是什么？
No response
补充信息
No response
Contribution
- 我愿意自己提交修复此 bug 的 PR（请先等待维护者在本 issue 中批准）
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by opening the reported Kimi web page in a browser and inspecting the WASM response headers and loading error. Then trace the web asset-serving entry point in this TypeScript repository; done means WASM responses use Content-Type application/wasm and load through the streaming path rather than ArrayBuffer. No file or test is named, so locate the relevant serving code and the nearest available check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, wasm
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100