Nimblesite / Nimblesite/SharpLsp
Profiler: default output paths are CWD-relative and ProfilerConfig.output_directory is dead
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 132
- Forks
- 5
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 27
Description
From the multi-agent audit (src/profiler/trace.rs ~311): default trace/profile outputs go to .sharplsp/profiles relative to the HOST'S current directory. Editors commonly launch language servers with cwd = the editor install dir (Program Files on Windows) — writes fail with Access denied. The ProfilerConfig.output_directory setting exists but is never honored.
Fix: root defaults at the workspace root (or a per-user data dir), honor output_directory, and surface a clear error when the target is unwritable.
Contributor guide
No contributing guide indexed for this repository
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 at src/profiler/trace.rs around line 311 and trace how ProfilerConfig.output_directory is defined and consumed. Verify the workspace-root or per-user default behavior and test an unwritable target; done means configured output directories are honored and failures produce a clear error instead of silently using the host CWD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100