Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] workspaceSymbol LSP operation crashes with undefined is not an object (evaluating 'f.location.range.start')

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

Error performing workspaceSymbol: undefined is not an object (evaluating 'f.location.range.start')

Code Example

Error performing workspaceSymbol: undefined is not an object (evaluating 'f.location.range.start')

---

{
  "systemverilog": {
    "command": "slang-server",
    "args": [],
    "extensionToLanguage": {
      ".sv": "systemverilog",
      ".svh": "systemverilog",
      ".v": "verilog",
      ".vh": "verilog"
    }
  }
}
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Disclaimer: I'm filling this bug report on behalf of Claude Code, I first asked if could possibly be a bug with the lang server that I use slang-server and it honestly said no, and provided a potential fix too.

Conclusion: this is a Claude Code client bug, not a Slang bug. Slang is probably spec-compliant. The report should go to the Claude Code team, not the Slang developer. The fix is to guard against missing range:

// before: f.location.range.start

// after: f.location.range?.start

The operation crashes before returning any results, making workspace-wide symbol search completely unusable. The client code unconditionally accesses f.location.range.start but LSP 3.17 allows WorkspaceSymbol.location to omit range (partial location, resolved lazily via workspaceSymbol/resolve). When a compliant server returns the partial form, the access throws undefined is not an object (evaluating 'f.location.range.start').

What Should Happen?

workspaceSymbol should return a list of matching symbols with their file locations, allowing navigation to any symbol definition across the workspace without reading files manually.

Error Messages/Logs

Error performing workspaceSymbol: undefined is not an object (evaluating 'f.location.range.start')

Steps to Reproduce

  1. Open a project with a Slang language server configured
  2. Call the workspaceSymbol LSP operation on any file

This is the LSP config of my plugin:

{
  "systemverilog": {
    "command": "slang-server",
    "args": [],
    "extensionToLanguage": {
      ".sv": "systemverilog",
      ".svh": "systemverilog",
      ".v": "verilog",
      ".vh": "verilog"
    }
  }
}

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.136 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#callback error#memory management#API rate limit#retriever error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] workspaceSymbol LSP operation crashes with undefined is not an object (evaluating 'f.location.range.start')