Windows: verify it, or document that it is not supported
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- linux, macos, python
- Domain
- ci-cd, cli, documentation, testing
Research direction
Start with tests/run.py, the CLI shell command handling, cobalto debug's lldb-dap lookup, remote-sim, and the extension's Windows CLI path. Run python3 tests/run.py and the example project on Windows with GnuCOBOL, recording any changes needed; also inspect the CI configuration for a Windows job. The issue is done when Windows support is verified with a CI job, or the Linux and macOS support decision is documented in the README with WSL guidance.
Written by the indexing model from the issue text.
Description
Nobody has tried Cobalto on Windows. These parts are the most likely to need work:
- The CLI runs the commands of a profile through the shell, so a profile written for sh may need a Windows variant.
cobalto debuglooks for lldb-dap with an sh command line.remote-simrunssh -cand sh scripts.- The extension resolves the CLI in
.venv\Scripts\cobalto.exeon Windows, but only a unit test covers that path.
What would close this
One of the two:
- a run of
python3 tests/run.pyand of the example project on Windows with GnuCOBOL, with what had to change, and a Windows job in CI; or - a decision to support only Linux and macOS, with Windows through WSL, written in the README.
Reports from anyone who tries it are welcome, partial ones too. This is one of the rows of the roadmap to 1.0.
- 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
-
hive size:simple
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
painted-porch/marcus#977 ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day