Verify the VS Code extension end to end on Linux

Open
#13 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
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, linux, python, vscode
Domain
devtools, testing

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

extension help wanted

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-vscode passing on Linux. It looks for VS Code in /Applications on macOS; on Linux the COBALTO_VSCODE variable 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 readMemory or writeMemory, and the extension falls back to lldb's memory read and memory 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

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 abstracta/cobalto

All issues in abstracta/cobalto

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.