OpenVoiceOS / OpenVoiceOS/ovos-workshop
Echo fallback request ids in pongs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 17
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 36
Description
When core scopes fallback pings with a request id, fallback skills need to echo that id in the pong. Without that echo, concurrent fallback collectors cannot reliably separate replies from neighboring requests.
Keep legacy behavior unchanged when no request id is present.
Contributor 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.
Research direction
Start by locating the fallback ping and pong handling described in the issue, then trace how request ids are carried through fallback skills. Confirm that a present request id is echoed in the pong while responses without one retain legacy behavior; add or update coverage if the relevant tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100