Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Treat low-evidence candidate speech as unassessed

未关闭
  • 哪里不对？
#553 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Danielncku 已经在做这个了。

开始于 2026年10月30日。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
backend

调研方向

Read PR #423 and follow-up issues #123 and #553 to understand the existing communication eligibility flow. Locate where candidate turns determine assessment eligibility and review how transcript data is recorded and used. Agree on a deterministic evidence threshold before implementation; done means the listed transcript cases leave communication unassessed when evidence is insufficient, with coverage for each case.

由索引模型根据 Issue 内容生成。

描述

Background

PR #423 fixed the zero-candidate-turn case by leaving communication
unassessed when no candidate speech was recorded.

(guys can check out pr#423 first before fixing this issue)

However, the current assessment eligibility is still mainly determined by
whether at least one candidate turn exists. A transcript segment containing
a cough, background noise, a filler word, or a stray ASR result may therefore
enable communication scoring even when there is not enough meaningful
evidence to evaluate the candidate.

This is a follow-up to #123 and #423.

Current behavior

A session may be treated as communication-assessable as soon as one
candidate turn is recorded.

For example, the following may potentially count as evidence:

  • A cough or background noise transcribed as text
  • Filler-only speech such as "uh" or "um"
  • A short acknowledgement such as "yes"
  • A stray or malformed ASR transcript
  • Interviewer audio captured again through microphone echo

This may cause the report to generate a communication score and strengths
that are not supported by meaningful candidate speech.

Expected behavior

Communication should only be assessed when the transcript contains enough
meaningful candidate speech to support a reliable evaluation.

Sessions should distinguish between at least these states:

  • No candidate speech captured
  • Candidate speech captured, but evidence is insufficient
  • Sufficient evidence for communication assessment

For the first two states:

  • communicationScore should remain null
  • Communication should be displayed as unassessed
  • Communication strengths should not be invented
  • Coding activity, test runs, and code comments should not be treated as
    spoken communication

Proposed direction

Introduce a deterministic communication-evidence classification instead of
using only candidate_turns > 0.

The exact threshold should be discussed before implementation. Possible
signals include:

  • The number of substantive candidate turns
  • The amount of meaningful transcript content
  • Filtering filler-only and noise-like transcripts
  • Speaker attribution and ASR confidence, when available

The implementation should avoid relying on a model alone to decide whether
the available evidence is sufficient.

Validation

Add coverage for:

  • Zero candidate turns
  • Noise-only or cough-like transcripts
  • Filler-only speech
  • A single short acknowledgement
  • One substantive explanation
  • Multiple meaningful candidate responses
  • Mixed noise and meaningful speech
  • Empty or malformed ASR results
  • Interviewer echo incorrectly captured as candidate speech

Out of scope

This issue does not require implementing general-purpose audio denoising or
speaker recognition. Its scope is deciding whether the recorded transcript
contains enough reliable candidate evidence for communication assessment.

主要语言
Rust
星标
215
派生
141
平均合并
1 天 12 小时
30 天内合并 PR
232

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

sysprog21/codetrial 的其他 Issue

查看 sysprog21/codetrial 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。