rescript-lang / rescript-lang/rescript-vscode

Complaining about files that are long deleted

Open
#1,099 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
ReScript
Stars
354
Forks
63
Avg merge
11h 29m
Merged PRs (30d)
1

Description

Each time I start Zed I get this error. This refers to a file that was deleted weeks ago. I can't figure out where the cache is or how to delete it. I've tried removing the node_modules folder and other steps but it keeps hanging around. I don't have any ReScript stuff installed globally. I don't see this error in VS Code Output window. Any suggestions?

ReScript tooling: Internal error. Something broke. Here's the error message that you can report if you want:
    
Error: Command failed: /Users/justinmagaram/Library/Application Support/Zed/extensions/work/rescript/node_modules/@rescript/language-server/analysis_binaries/darwinarm64/rescript-editor-analysis.exe codeAction /Users/justinmagaram/Source/hot/src/stories/ShowStrokeView2Props.res 0 0 0 0 /var/folders/nh/4c3_nmmd3fs41j1lb6vzmvth0000gn/T/rescript_format_file_82416_1.res
Fatal error: exception Sys_error("/Users/justinmagaram/Source/hot/src/stories/ShowStrokeView2Props.res: No such file or directory")


(this message will only be reported once every 15 minutes)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the startup error in the Zed extension at /Users/justinmagaram/Library/Application Support/Zed/extensions/work/rescript and inspect how it invokes @rescript/language-server for the deleted ShowStrokeView2Props.res file. Confirm the stale reference is cleared or ignored so starting Zed no longer reports an error for that file.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.