Go client: no typed RunSweep wrapper — the sweep RPC is unreachable and the parity doc claims RPC coverage
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 58/100
Research direction
Read client/opensysml/client.go and client/opensysml/runs.go, then compare their request and response conversions with api/proto/sysml.proto and the handler in internal/frontend/grpc/sweep.go. Implement the typed client wrapper and preserve the response fields listed in the issue. Done means callers can invoke the sweep RPC through the Go client and receive its table and metadata; update docs/reference/client-parity.md to resolve its contradictory coverage claims.
Written by the indexing model from the issue text.
Description
Disclaimer, this issue was detected and written by an AI
Summary
The service has a RunSweep RPC that answers a table of run rows for a parameter
sweep. Every other client wraps it. client/opensysml has no RunSweep method at
all; a caller can only reach a sweep indirectly through RecordRun.
docs/reference/client-parity.md contradicts itself: "Every client exposes all 31
RPCs ... as typed calls", while the Open gaps table says "the package has no typed
RunSweep wrapper at all" (estimate about one day).
Service contract (already implemented)
api/proto/sysml.proto:
RunSweepRequest: model_hash, symbol_id (FQN of an analysis case or calc,
definition or usage), subject_symbol_id, positional arguments, named
named_arguments, ranges (SweepRange: parameter, start, end, step),
samples (draw uniformly; 0 steps; above 0 needs a seed and refuses a range with
a step), seed, engine.
RunSweepResponse: rows (SweepRow: inputs, outputs, verdicts,
elapsed_micros, error, failure_reason, evaluations), parameters,
sampled, seed, error, diagnostics, failure_reason, instances,
engine, strength, bounds.
The handler is internal/frontend/grpc/sweep.go:29; it requires
CapabilityVerification (not runs), and already checks ctx.Err() per
table at :143. A pre-run failure is a 200 with RunSweepResponse.error +
failure_reason; a failed row is a row, not a table error.
Current client state
client/opensysml/client.goClient:RunAction/RunMonteCarlo(RunRuns)
but noRunSweep.client/opensysml/runs.go:284—runRowsFromProtoalready decodes
[]*pb.SweepRow, but onlyInputs,Outputs,Verdicts,Error
(RunRowatruns.go:37).elapsed_micros,failure_reasonand
evaluationsare dropped.runs.go:439—RecordRange(parameter, start, end, step)already builds a
pb.SweepRange, so the range/value conversion exists.runs.go:517—Recording.Sweepuses the same decoder.
Required API
// SweepRange is one parameter stepped (or drawn) from start to end.
type SweepRange struct {
Parameter string
Start, End, Step Value // Step is nil for a sampled sweep
}
// Sweep is what a sweep answers: the table and the parameters it covered.
type Sweep struct {
Rows []RunRow
Parameters []string
Sampled bool
Seed uint64
Diagnostics []Diagnostic
Instances []*Instance // when the type already maps (analysis.go)
Engine string
Strength string
Bounds []Bound
}
type SweepOption func(*sweepOptions)
func SweepSubject(symbolID string) SweepOption
func SweepArguments(values ...Value) SweepOption
func SweepArgument(name string, value Value) SweepOption
func SweepSamples(rows int64) SweepOption
func SweepSeed(seed uint64) SweepOption
func SweepEngine(name string) SweepOption
// Sweep runs the analysis case or calc over the ranges and answers one row per
// run, in the service's order. Requires the verification capability.
func (c *client) Sweep(ctx context.Context, model *Model, symbolID string,
ranges []SweepRange, opts ...SweepOption) (*Sweep, error)
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
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
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