OpenVoiceOS / OpenVoiceOS/ovos-skill-count

"count to 3" unmatched through the padatious pipeline on dev

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2
Forks
3
Avg merge
2d 1h
Merged PRs (30d)
19

Description

🤖 Auto-generated by Claude Fable 5 (claude-fable-5) via Claude Code — NOT human-reviewed. Verify before acting.

Deterministic on current dev (5/5 runs, verified on an unmodified clone): the end2end bus round-trip for "count to 3" through ovos-padatious-pipeline-plugin-high never matches count_to_n — capture shows only recognizer_loop:utterance → play_sound → ovos.intent.unmatched → ovos.utterance.handled (test/end2end/test_stop.py::TestCountSkills::test_count_to_n_routes_and_speaks). The padacioso path matches the same utterance fine, and loading the intent file standalone raises no expansion-cap warning — the defect is specific to the padatious training/routing of this skill's 5254-line count_to_n.intent. Suspect the file's size interacts badly with padatious training (timing or sampling); needs a padatious-side reproduction with this exact file. Not caused by any open PR — the failure reproduces identically without them.

Contributor guide

Open the 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.

Research direction

Start with test/end2end/test_stop.py::TestCountSkills::test_count_to_n_routes_and_speaks and reproduce the failure on an unmodified clone. Compare padatious with the working padacioso path using the 5254-line count_to_n.intent file; done means the end-to-end "count to 3" route matches count_to_n and speaks instead of producing ovos.intent.unmatched.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.