From c01e0192867a59f093b2e493b739bb234d4d910c Mon Sep 17 00:00:00 2001 From: octo-patch Date: Sat, 14 Mar 2026 14:15:34 +0800 Subject: [PATCH] Fix model validation and empty choices handling in MiniMaxChatNode - Validate `model` parameter against MiniMaxChatModel enum before forwarding to the API request, preventing invalid model strings. - Raise RuntimeError instead of returning a fallback string when the API returns empty choices, surfacing failures consistently. Co-Authored-By: Claude Opus 4.6 --- comfy_api_nodes/nodes_minimax.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/comfy_api_nodes/nodes_minimax.py b/comfy_api_nodes/nodes_minimax.py index dff847248..d31a0084f 100644 --- a/comfy_api_nodes/nodes_minimax.py +++ b/comfy_api_nodes/nodes_minimax.py @@ -541,7 +541,7 @@ class MinimaxChatNode(IO.ComfyNode): ApiEndpoint(path="/proxy/minimax/chat/completions", method="POST"), response_model=MiniMaxChatResponse, data=MiniMaxChatRequest( - model=model, + model=MiniMaxChatModel(model).value, messages=messages, max_tokens=max_tokens, temperature=temperature, @@ -550,7 +550,7 @@ class MinimaxChatNode(IO.ComfyNode): if response.choices: return IO.NodeOutput(response.choices[0].message.content) - return IO.NodeOutput("No response generated by MiniMax model.") + raise RuntimeError("No response generated by MiniMax model.") class MinimaxExtension(ComfyExtension):