Verify the VS Code extension end to end on Linux
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with vscode-cobalto/DEVELOPMENT.md and test/linux/run.sh, then find how run-in-vscode reads COBALTO_VSCODE on Linux. Run the extension check in real VS Code, ideally under a virtual display in CI, and record or fix any failures. Done when the Linux check passes, the extension README documents any unresolved findings, and the roadmap extension row is updated.
Written by the indexing model from the issue text.
Description
On macOS the extension is verified inside a real VS Code by run-in-vscode: activation, Test Explorer, the list of profiles, coverage and three debug sessions (see DEVELOPMENT.md). On Linux only part of that has run: test/linux/run.sh builds a Docker image (Ubuntu 24.04, GnuCOBOL 3.1.2, lldb-dap 18) and runs the suites, cobalto debug and the debug adapter check verify-dap, but not the extension inside VS Code.
What would close this
-
run-in-vscodepassing on Linux. It looks for VS Code in/Applicationson macOS; on Linux theCOBALTO_VSCODEvariable gives it the executable. - Ideally, the same check in CI, with VS Code under a virtual display.
- Whatever it finds fixed, or written down in the extension's README. One difference is already handled: lldb-dap 18 has no
readMemoryorwriteMemory, and the extension falls back to lldb'smemory readandmemory write. - The extension row of the roadmap updated.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 abstracta/cobalto
-
extension help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
compiler help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
release
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in abstracta/cobalto
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9128 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/extensions#975 ·
Maintainers usually reply within 1 day
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-python#1789 ·
Maintainers usually reply within 9 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
juandresrodca/AdminForge#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day