brailcom/speechd

messages of killed clients don't get interrupted

Open

#942 opened on Jul 10, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (86 forks)auto 404
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (325 stars)
PR merge metrics
 (PR metrics pending)

Description

Steps to reproduce

  • make orca produce long message
  • kill it -KILL

Obtained behavior

  • the message continues

Expected behavior

  • we'd want the message to stop, so that e.g. orca -r restarts speech immediately

Behavior information

  • we however don't want the message of spd-say without -w to be stopped

Contributor guide

Research direction
Investigate the message sending mechanism in the server when a client is killed (e.g., with KILL) and identify where the interruption should occur to stop the message output.
Tech stack
c
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70