一句话：通过对 203 个 GitHub Bug 报告线程的定性分析，揭示毒性源于严重度/优先级认知错位等，并损害协作与修复结果。
本文关注开源协作中 Bug 报告讨论里的毒性行为。Bug 报告以问题为中心且情绪化，容易滋生毒性互动，但相关理解仍有限。作者对 GitHub 上 203 个 Bug 线程进行定性分析，其中 81 个包含毒性言论。研究发现，毒性常源于对缺陷严重度与优先级的认知不一致、对工具的不满与未解决挫败感，以及专业沟通规范的缺失。毒性互动不仅使讨论偏离正轨，还降低可操作结果出现的可能性，例如将 issue 与 pull request 关联。最后，论文提出可操作建议，通过缓解毒性来改善 Bug 修复。
Toxicity in bug report discussions poses significant challenges to the collaborative dynamics of open-source software development. Bug reports are crucial for identifying and resolving defects, yet their inherently problem-focused nature and emotionally charged context make them susceptible to toxic interactions. This study explores toxicity in GitHub bug reports through a qualitative analysis of 203 bug threads, including 81 toxic ones. Our findings reveal that toxicity frequently arises from misaligned perceptions of bug severity and priority, unresolved frustrations with tools, and lapses in professional communication. These toxic interactions not only derail productive discussions but also reduce the likelihood of actionable outcomes, such as linking issues with pull requests. Our preliminary findings offer actionable recommendations to improve bug resolution by mitigating toxicity.