MoonshotAI / MoonshotAI/kimi-code
kimi web bug:”WireError: Unknown wire record type 'micro_compaction.apply' skipped during restore”
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What version of Kimi Code is running?
0.28.1
Which open platform/subscription were you using?
kimi code Allegro
Which model were you using?
k3
What platform is your computer?
No response
What issue are you seeing?
[unexpected] WireError: Unknown wire record type 'micro_compaction.apply' skipped during restore
at WireService.reportSkippedRecord (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:256925:22)
at WireService.replayRecord (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:256907:10)
at WireService.restore (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:256887:11)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async AgentLifecycleService.doCreate (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:281753:5)
at async AgentLifecycleService.create (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:281726:12)
at async SessionLifecycleService.doResume (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:284496:39) {
code: 'wire.unknown_record',
details: { type: 'micro_compaction.apply', index: 1035 }
}
What steps can reproduce the bug?
……
What is the expected behavior?
No response
Additional information
No response
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 tracing WireService.restore, replayRecord, and reportSkippedRecord in the generated dist-native bundle, then follow AgentLifecycleService.doCreate and SessionLifecycleService.doResume from the stack trace. Reproduce the restore failure with Kimi Code 0.28.1 on the Allegro subscription and document the expected behavior, since the issue currently provides no reproduction steps or expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100