MoonshotAI / MoonshotAI/kimi-code
Startup failure points to a log file that was never created
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What happens
On a fresh data dir (or any early-exit failure before the logger initializes):
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 reproducing the startup failure with a fresh data directory and with a failure before logger initialization. Trace the CLI startup error path and logging setup to find where the nonexistent log-file path is reported. Done means the failure message no longer points to a log file that was never created.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100