Restore sidecar coverage gates for diagnostic and SDK restore lifecycles
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start by inspecting the Release sidecar coverage reports and the existing diagnostic pipeline tests; the issue identifies compiler IPC and SDK restore lifecycles as the paths needing coverage. Add integration coverage for the listed startup, script membership, overlay, package cache, restore failure, and workspace notification cases, then run the fresh sidecar coverage gate. Done means the unchanged F# and Common effective floors pass.
Written by the indexing model from the issue text.
Description
The complete Release sidecar coverage run at 0b6e2677 failed the existing release floors after the diagnostic pipeline expanded.
Observed coverage from the actual XPlat reports:
- C#: 8423/8740 = 96.3730%, passes.
- F#: 3302/3586 = 92.0803%, below the 95% floor (94% effective).
- Common: 1106/1171 = 94.4492%, below the 96.06% floor (95.06% effective).
Keep all floors unchanged. Exercise the new paths through real compiler IPC and real SDK restore lifecycles, including compiler startup failures, script source membership, closed overlays, missing package caches, restore failure, and negotiated workspace completion notifications.
d9592226 adds five real IPC scenarios and passes all 468 F# cases in Release with coverage: 3383/3586 = 94.3391%, meeting the existing effective gate. Common restore integration coverage and a complete fresh sidecar gate remain required.
- Dominant language
- TypeScript
- Stars
- 168
- Forks
- 9
- Avg merge
- 2h 51m
- Merged PRs (30d)
- 59
Getting set up
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
- 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.
More from Nimblesite/SharpLsp
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Nimblesite/SharpLsp#468 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Nimblesite/SharpLsp#461 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Nimblesite/SharpLsp#447 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Nimblesite/SharpLsp#444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Nimblesite/SharpLsp#442 ·
Maintainers usually reply within 1 day
All issues in Nimblesite/SharpLsp
Similar issues
-
a10y a10y-audit ai-driven-qa claude
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
linagora/twake-directory-manager#219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installsPossibly taken @zephyr91 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2393 ·
Maintainers usually reply within 4 days