Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Just My Code and exception caller projection misclassify symbol-bearing sibling libraries

Open
  • Is something wrong?
#430 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
testing-qa

Research direction

Start by locating the Just My Code and external_code=user-boundary exception projection logic, then read the regression matrix described in the issue. Reproduce the six Windows VSIX failures with portable PDBs and compare launch-root behavior with workspace fallback. Done means the matrix passes while user throws, unhandled-only controls, caller source and line, and exceptionInfo preservation remain correct.

Written by the indexing model from the issue text.

Description

Real Windows VSIX exception matrix reproduces six failing C#/F# cases when an external library has portable PDBs and sits inside a broader workspace but outside the explicit launch cwd. Just My Code incorrectly surfaces handled library throws, and external_code=user-boundary incorrectly leaves the library throw frame visible. Root cause: workspace membership OR launch-root membership lets the broad workspace override the explicit source boundary. Regression matrix covers just_my_code on/off crossed with throw-site/user-boundary, original external source/PDBs, caller source/line, exceptionInfo preservation, user throws and unhandled-only controls. Fix makes the explicit launch root authoritative, with workspace fallback when no launch root is available.

Dominant language
TypeScript
Stars
168
Forks
9
Avg merge
2h 51m
Merged PRs (30d)
59

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from Nimblesite/SharpLsp

All issues in Nimblesite/SharpLsp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.