-
Notifications
You must be signed in to change notification settings - Fork 660
[format] Valid para format error info #4035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Jiang-Jia-Jun
merged 16 commits into
PaddlePaddle:develop
from
xiaolei373:valid_para_format_error_info
Sep 12, 2025
Merged
[format] Valid para format error info #4035
Jiang-Jia-Jun
merged 16 commits into
PaddlePaddle:develop
from
xiaolei373:valid_para_format_error_info
Sep 12, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your contribution! |
6976e04 to
5270dd5
Compare
5270dd5 to
3f3c012
Compare
sunlei1024
approved these changes
Sep 12, 2025
Jiang-Jia-Jun
approved these changes
Sep 12, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
本次改动主要包括以下两点:
请求参数超参数校验前置
ChatCompletionRequest/CompletionRequest类中。错误信息格式全局统一
错误响应格式与 OpenAI 对齐,统一为以下结构:
{ "error": { "message": "错误的详细描述(不为 null)", "type": "错误类别(可为 null)", "param": "具体出错的参数(可为 null)", "code": "细分错误类别(可为 null)" } }具体约定:
请求参数异常
message和param提供准确错误信息与参数名。type固定为"invalid_request_error"。code根据不同场景设置具体枚举值(如"invalid_value")。示例:
{ "error": { "message": "Input should be a valid integer, got a number with a fractional part", "type": "invalid_request_error", "param": "max_tokens", "code": "invalid_value" } }引擎或底层推理错误
message字段中。type固定为"internal_error"。