Query: expose the verify link, connection/attachment properties, and TransitionUsage rows
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 28/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- backend-api-design
Línea de trabajo
Start with the query property implementation and wire-contract list, then read the query tests and api.md around add_verify. Trace how the grammar builds TransitionUsage and how the index turns it into an ActionUsage; probe the existing connector and port model to find their relationship facts. Done means verification, port graph, and transition rows are queryable, with the stated fixtures and unknown-property refusals passing.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Disclaimer, this issue was detected and written by an AI
Summary
Three relationship facts are in the model but not in the query substrate, so the
cross-view warnings and the M5 cyclomatic metric cannot be projections:
- verify link —
satisfiedRequirement/satisfyingFeaturecoversatisfy;
a verification case'sverifyobjective has no queryable property, so the
verifier half of the consistency check is engine-capable-blocked. - connection/attachment — a port graph (which connector/attachment reaches
a port) is not queryable, so the port-mismatch warning bucket is not a
predicate. - TransitionUsage rows — a
transitionanswers no row of its own; it is an
anonymousActionUsage, so per-machineE − N + 2Pcannot be computed from
the same answer. Probed at 0.12.1: a fixture with
transition t1 first a if true then b;answers 6 rows —Package,
StateDefinition,StateUsage×3,ActionUsage×1 — and no
TransitionUsage.
Proposal
- Add the verify analogue of the satisfy pair. Suggested names after a probe:
verifiedRequirement(the requirement averifymembership names) and
verifyingCase(the verification case whose objective holds it), each absent
when unresolved or not a verify membership.add_verifyalready writes the
membership (api.md:192), so the relationship is expressible. - Add connection/attachment properties, named after the metamodel fact they
report (probe first): e.g. aconnection/attachmentproperty on a connector
usage and the reaching connector(s) on a port usage, or a pair of endpoint
properties. Whatever the names, make the port graph answerable in one scoped
query without a per-elementGetSymbolfan-out. - Make a transition answer a row:
@type=TransitionUsage, with@id,owner,
name, and its source/target (or the succession ends as properties). The
grammar already buildsTransitionUsages; the index/query answer must stop
flattening them into an anonymousActionUsage.
Tests
- A state-machine fixture:
TransitionUsagerows count and owner; the same
E − N + 2Pderivation the metric would use. - A verification fixture:
verify Req;inside a case's objective answers
verifiedRequirement/verifyingCase; asatisfystays on the existing pair. - A connector/port fixture: the port graph is answerable and the mismatch
predicate can be written without a lookup per element. - Keep
unknown propertyrefusals for names outside the grown set.
Acceptance
- The verifier half and the port-graph bucket are query predicates.
- A transition is its own row with identity and owner.
- Wire-contract list and query tests move together.
- Lenguaje dominante
- Go
- Estrellas
- 59
- Forks
- 20
- Merge medio
- 10 h 23 min
- PR fusionados (30 d)
- 897
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Open-MBEE/OpenSysML
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
A model's parse is still paid cold in every process; the library record cache does not cover itAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 56/100
Los mantenedores suelen responder en 1 día
Todos los issues de Open-MBEE/OpenSysML
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
krakenhavoc/cmd_and_ctrl#5853 ·
Los mantenedores suelen responder en 1 día
-
flaky test: TestTRTAsyncPrefillFailures/transport reads the token load before prefillDone has released itPosiblemente ocupada @Jackmeson1 la tomó hoy. Abiertoarea/cicd area/gateway kind/misc
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
vllm-project/aibrix#3488 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Type: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
projectdiscovery/httpx#2735 ·
Los mantenedores suelen responder en 1 día
-
NuGet registry builds every URL from ROOT_URL, ignoring the host the client usedPosiblemente ocupada @gritse la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día