Seek .(US:SKLTY) 3 6 Ke·2025-08-27 07:44Core Viewpoint - The recent issues with Tencent's Codebuddy and Byte's Trae are attributed to a bug in the DeepSeek V3.1 model, which has led to unexpected outputs in code generation, particularly the insertion of the character "极" [1][4][12]. Group 1: Bug Discovery and Impact - Users reported that while using Tencent's Codebuddy, unexpected advertisements were inserted into the code, leading to uninstallation by some users [1]. - The bug was identified as originating from the DeepSeek V3.1 model, with users noting that it could generate the character "极" in unexpected places [4][12]. - A developer on Reddit confirmed similar issues with DeepSeek V3.1, indicating that the model produced unexpected tokens during testing [4]. Group 2: User Experiences and Variability - Some users reported that they did not encounter the bug when using DeepSeek's official API, while third-party platforms showed a higher incidence of the issue [6]. - The bug has been humorously referred to as the "极你太美" incident by users, highlighting the community's engagement with the issue [7]. - Feedback from users indicated that the problem was not isolated to DeepSeek, with other models like Gemini and Grok also exhibiting similar issues [12]. Group 3: Theories on Bug Origin - Various hypotheses have been proposed regarding the cause of the bug, including token continuity issues, data contamination during training, and problems with the multi-token prediction framework [14][16]. - A researcher suggested that the bug might be linked to the self-supervised synthetic data used during the fine-tuning phase of the model [16]. - The persistence of the "极" issue across different versions of the model suggests a deeper problem with the training data and model architecture [18]. Group 4: Community Response and Future Considerations - The community has actively engaged in identifying and discussing the bug, with developers calling for better monitoring and cleaning mechanisms throughout the model training process [18]. - The incident has highlighted the importance of collaborative problem-solving in the open-source community, with users expressing optimism about collectively addressing the issue [18].