[GH-ISSUE #30] BadRequestError: Error code: 400 - {'detail': 'Content Exists Risk'} #29

Open
opened 2026-10-26 21:06:57 +00:00 by bsakaguchi · 6 comments
Owner

Originally created by @judeomg on GitHub (May 15, 2024).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V2/issues/30

API调用时,这个错误是什么原因引起的?token超出限制吗?那么该如何确保token不超出限制呢?

Originally created by @judeomg on GitHub (May 15, 2024). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V2/issues/30 API调用时,这个错误是什么原因引起的?token超出限制吗?那么该如何确保token不超出限制呢?
Author
Owner

@qkxie commented on GitHub (May 16, 2024):

有敏感词。

<!-- gh-comment-id:2114059495 --> @qkxie commented on GitHub (May 16, 2024): 有敏感词。
Author
Owner

@williamjeong2 commented on GitHub (May 16, 2024):

Too many sensitive words. Uncomfortable to use in real life.

<!-- gh-comment-id:2114890408 --> @williamjeong2 commented on GitHub (May 16, 2024): Too many sensitive words. Uncomfortable to use in real life.
Author
Owner

@qkxie commented on GitHub (May 17, 2024):

Toooooo many sensitive words. In China, we call this situation self-castration.

<!-- gh-comment-id:2116484861 --> @qkxie commented on GitHub (May 17, 2024): Toooooo many sensitive words. In China, we call this situation self-castration.
Author
Owner

@luofuli commented on GitHub (May 28, 2024):

Please retry the API now. We've updated the content safety strategies.
@judeomg

<!-- gh-comment-id:2134616307 --> @luofuli commented on GitHub (May 28, 2024): Please retry the API now. We've updated the content safety strategies. @judeomg
Author
Owner

@qkxie commented on GitHub (May 28, 2024):

@luofuli This error still exists. My dataset is 100 comments of Xiaohongshu. When I want to use deepseek to analyze the sentiment of these comments, this error raised. I have retry for different keyword in Xiaohongshu, and almost any 100 comments of any notes of any keyword will trigger your stupid risk alarm.

<!-- gh-comment-id:2134626608 --> @qkxie commented on GitHub (May 28, 2024): @luofuli This error still exists. My dataset is 100 comments of Xiaohongshu. When I want to use deepseek to analyze the sentiment of these comments, this error raised. I have retry for different keyword in Xiaohongshu, and almost any 100 comments of any notes of any keyword will trigger your stupid risk alarm.
Author
Owner

@qkxie commented on GitHub (May 28, 2024):

This system and message will trigger the alarm:

system = '你是一个非结构化数据转结构化的提取专家。善于从长文本中提取出结构化的信息。'

msg = '''我会给你一段文本,文本中提到了对某赛道,可以按类别进行拆分,也可能按应用进行拆封。你需要把拆封结果提取出来,并以JSON格式返回。

例如:

输入:

` ``
本文重点关注如下国家或地区:
    北美(美国和加拿大)
    欧洲(德国、英国、法国、意大利和其他欧洲国家)
    亚太(中国、日本、韩国、中国台湾地区、东南亚、印度等)
    拉美(墨西哥和巴西等)
    中东及非洲地区(土耳其和沙特等)
按产品类型拆分,包含:
    单相
    三相
按应用拆分,包含:
    音视频设备
    电源
    电信系统
    其他
` ``

输出: {{"category": ["单相", "三相"], "application": ["音视频设备", "电源", "电信系统", "其他"]}}

只需要提取类别和应用的拆分就可以了。其他拆分不需要提取。如果没有按应用拆封,就不反悔application字段。

现在,请从下面的文本中提取:'''

And you will get the alarm.

image

<!-- gh-comment-id:2134643256 --> @qkxie commented on GitHub (May 28, 2024): This system and message will trigger the alarm: ``` system = '你是一个非结构化数据转结构化的提取专家。善于从长文本中提取出结构化的信息。' msg = '''我会给你一段文本,文本中提到了对某赛道,可以按类别进行拆分,也可能按应用进行拆封。你需要把拆封结果提取出来,并以JSON格式返回。 例如: 输入: ` `` 本文重点关注如下国家或地区: 北美(美国和加拿大) 欧洲(德国、英国、法国、意大利和其他欧洲国家) 亚太(中国、日本、韩国、中国台湾地区、东南亚、印度等) 拉美(墨西哥和巴西等) 中东及非洲地区(土耳其和沙特等) 按产品类型拆分,包含: 单相 三相 按应用拆分,包含: 音视频设备 电源 电信系统 其他 ` `` 输出: {{"category": ["单相", "三相"], "application": ["音视频设备", "电源", "电信系统", "其他"]}} 只需要提取类别和应用的拆分就可以了。其他拆分不需要提取。如果没有按应用拆封,就不反悔application字段。 现在,请从下面的文本中提取:''' ``` And you will get the alarm. ![image](https://github.com/deepseek-ai/DeepSeek-V2/assets/134578340/36b2d286-c40c-4d24-a859-fb6734dde3bb)
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepSeek-V2#29
No description provided.