help lexicon-import: crashes with 'No CLI usage line is catalogued' (exit 134)

Open Beginner friendly
#261 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
cli

Research direction

Start in src/SIL.Motif.Cli/HelpCommand.cs, especially UsageLines and PrintEntry, which the exception trace identifies. Run motif help lexicon-import to reproduce the crash, then inspect the help catalog and existing tests to see how topics without usage lines are represented. Done when this topic prints without an exception and a test covers help output for catalogued topics.

Written by the indexing model from the issue text.

Description

motif help lexicon-import (with or without --full) prints the topic text, then crashes with exit 134.

Build: a16a78878312 (windows/main, 2026-11-17), Release, Linux.

Output (tail):
System.IO.InvalidDataException: No CLI usage line is catalogued for 'lexicon-import'
at SIL.Motif.Cli.HelpCommand.UsageLines (src/SIL.Motif.Cli/HelpCommand.cs:296), called from PrintEntry (line 331) and Run (line 138).

The #252 reply points agents to motif help lexicon-import (Attribution section) for the attribution composers, so this is where they'll look first.

Expected: the topic prints with no exception. A topic with no command (or no usage line) should skip the usage block. It would also help to have a Help golden or test that runs help <topic> for every catalogued topic.

Next: catalogue the usage line, or let topics without one skip the block, and add a test across all topics.

Dominant language
C#
Stars
1
Forks
0
Avg merge
4h 3m
Merged PRs (30d)
66

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sillsdev/motif

All issues in sillsdev/motif

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.