CLI: parsimony --measure refuses without a Baseline, while --group captures one
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Start with ParsimonyCommands.cs, comparing EnqueueGroup's Baseline capture with Enqueue, then read the CLI tests for parsimony commands. Add a test for running --measure with no Baseline when the requested Measures include a Grammar-group Measure, and check the help text in parsimony.md. Done means the command captures a Baseline in that case and the help page describes the behavior.
Written by the indexing model from the issue text.
Description
motif parsimony --measure <id> refuses for lack of a Baseline, while parsimony --group grammar captures one itself. A first run against a project with no Baseline fails as a semantic job failure; the person has to know to run baseline capture and try again. One whole-grammar run took three attempts this way.
What we know:
ParsimonyCommands.EnqueueGroupcaptures a Baseline when none is current;ParsimonyCommands.Enqueuedoes not.- The Help page
parsimony.mdsays "This command does not capture or refresh one", which CONTEXT's Grammar group entry contradicts. - Inferred: an earlier attempt's job sat unclaimed because a worker started by hand collided with the auto-started one; the auto-start (
ProcessRunnerLauncher) works when left alone.
Proposed change: Enqueue uses the same capture step as EnqueueGroup when the requested Measures (or all) include a Grammar-group Measure; the Help page says so. One shared helper in ParsimonyCommands.cs.
Next: factor the capture step out of EnqueueGroup and add a CLI test with no Baseline.
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- Avg merge
- 3h 55m
- Merged PRs (30d)
- 36
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 sillsdev/motif
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
Playground selection bar: comes back after Apply or scrolling while focus is in the Markdown paneOpentextediting
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
textediting
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
textediting
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
textediting
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
bug emitter:client:csharp
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/typespec#12572 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
AWS Lambda: KeyNotFoundException drops HTTP-triggered transactions when allowAllHeaders is disabledOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
newrelic/newrelic-dotnet-agent#3949 · 1 comment ·
Maintainers usually reply within 1 day
-
area-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/aspnetcore#70545 · 1 comment ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100