Go client: expose EngineInfo.kind and EngineInfo.protocol (the service already fills them)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with client/opensysml/engines.go and the EngineInfo definition in api/proto/sysml.proto; inspect how ListEngines maps the existing response fields. Update the Go client mapping and check client/opensysml/engines_test.go for the built-in and registered tool cases. Done when both values match the service and existing fields remain unchanged; the issue also calls for the Go cell in the parity test and documentation.
Written by the indexing model from the issue text.
Description
Disclaimer, this issue was detected and written by an AI
Summary
ListEnginesResponse carries each engine's origin and transport:
EngineInfo.kind (built-in, tool, engine, policy, sampler) and
EngineInfo.protocol (-, object, argv+<stdin>, <transport>/<protocol>).
The service fills both. client/opensysml drops them, so an in-process caller
cannot tell an engine's kind or how it is spoken to and falls back to forking
sysml -engines.
Current state
api/proto/sysml.proto::EngineInfo—kind = 9,protocol = 10.client/opensysml/engines.go:12—EngineInfohasName,Authority,
Answers,Bounds,Process,ProcessFound,Ready,Unavailable; no
Kind, noProtocol.ListEnginesatengines.go:115copies fields 1–8 only.
Proposal
- Add
Kind stringandProtocol stringtoEngineInfo, with the proto's
comments, and copye.Kind/e.ProtocolinListEngines. - No capability gate: the fields are part of the existing
enginesresponse.
Tests
client/opensysml/engines_test.go: a service with a built-in engine reports
Kind == "built-in"andProtocol == "-"; a registered tool reports its
manifest kind and<transport>/<protocol>spelling; the undecoded old fields
are unchanged.parity_options_test.go/parity doc: add the Go cell.
Acceptance
-
EngineInfo.Kind/.Protocolmatch the service for built-in and external
engines. - No new capability gate; existing
ListEnginescallers keep working.
- Dominant language
- Go
- Stars
- 59
- Forks
- 20
- Avg merge
- 10h 23m
- Merged PRs (30d)
- 897
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 Open-MBEE/OpenSysML
-
A model's parse is still paid cold in every process; the library record cache does not cover itOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
krakenhavoc/cmd_and_ctrl#5853 ·
Maintainers usually reply within 1 day
-
flaky test: TestTRTAsyncPrefillFailures/transport reads the token load before prefillDone has released itPossibly taken @Jackmeson1 claimed this today. Openarea/cicd area/gateway kind/misc
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vllm-project/aibrix#3488 · 2 comments ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
projectdiscovery/httpx#2735 ·
Maintainers usually reply within 1 day
-
NuGet registry builds every URL from ROOT_URL, ignoring the host the client usedPossibly taken @gritse claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day