fix(openai): tolerate empty content in forced tool choice by QwertyJack · Pull Request #40148 · vllm-project/vllm

QwertyJack · 2026-04-17T13:17:29Z

Summary

This fixes a forced-tool-choice crash when reasoning extraction returns content=None.

Some reasoning parsers, including the glm45 / DeepSeekV3ReasoningWithThinkingParser path, may consume the full model output and return (reasoning, None). The forced tool-choice branches in both chat-completions and responses parsing previously asserted that content is not None, which made this a server-side failure instead of a valid function call with empty arguments.

Changes

normalize content=None to "" in OpenAIServing._parse_tool_calls_from_content(...)
normalize content=None to "" in DelegatingParser._parse_tool_calls(...)
add regression tests for:
- chat-completions named tool_choice with content=None
- responses named tool_choice with content=None

Fixes #40147.

Testing

pytest -sv tests/entrypoints/openai/test_tool_choice_content_none.py

claude

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

gemini-code-assist

Code Review

This pull request updates the OpenAI serving engine and abstract parser to handle cases where a named tool choice is provided but the content is null. Specifically, it replaces assertions with a default empty string for the content variable, preventing potential runtime errors during forced function calls. Additionally, a new test suite has been added to verify this behavior for both Chat Completion and Responses APIs. I have no feedback to provide.

Backport the upstream forced-tool-choice fix to the v0.18.0 compatibility layer. Some reasoning parsers may consume the full model output and return content=None; normalize that to an empty argument string before the forced named tool-choice branches delegate back to upstream parsing. References: vllm-project/vllm#40147, vllm-project/vllm#40148 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com>

ywang96 · 2026-04-21T06:21:05Z

Is this PR still needed? cc @JaredforReal

…pty content (#8400) ### What this PR does / why we need it? This backports the forced-tool-choice `content=None` guard to the `releases/v0.18.0` compatibility layer. Upstream vLLM still has forced named tool-choice branches that assert `content is not None` after reasoning extraction. Some reasoning parsers can legally consume the full output and return `(reasoning, None)`, which makes the assert reachable and can surface as a server-side failure. This PR follows the same compatibility-patch pattern used by: - `7314bbe2` fix(platform): reimplement MiniMax usage accounting patch (#7835) - `f83cb0e6` [Bugfix][Platform] Fix GLM47 tool-call finish backfill (#7710) The patch is intentionally narrow: - normalize `content=None` to `""` only for forced named tool choice - patch both chat-completions and responses parser entry points - keep the rest of upstream behavior unchanged Upstream tracking: - issue: vllm-project/vllm#40147 - PR: vllm-project/vllm#40148 ### Does this PR introduce _any_ user-facing change? Yes. Forced named tool choice becomes robust when the reasoning parser returns no post-reasoning content, avoiding an internal assertion failure and emitting an empty-argument function call instead. ### How was this patch tested? Unit tests: ```bash pytest -sv tests/ut/patch/platform/test_patch_tool_choice_none_content.py \ tests/ut/patch/platform/test_patch_glm_tool_call_parser.py \ tests/ut/patch/platform/test_patch_minimax_usage_accounting.py ``` Result: 22 passed. --------- Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com>

mergify · 2026-04-28T09:06:14Z

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @QwertyJack.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

chaunceyjiang · 2026-04-28T09:07:01Z

Hi @QwertyJack Please fix the conflicts.

QwertyJack · 2026-04-28T10:58:14Z

@chaunceyjiang PTAL

chaunceyjiang · 2026-04-28T11:07:23Z

        ):
            # Named function with standard JSON-based parsing
-            assert content is not None
+            content = content or ""


I think that when content is None, arguments should be "{}"—"" is not a standard OpenAI-defined semantic representation.

chaunceyjiang · 2026-04-28T12:05:37Z

I feel that making modifications here is not very elegant. Perhaps it would be better to modify the corresponding parser.

Normalize None content to an empty argument string when forced tool choice runs after reasoning extraction. This avoids AssertionError in both chat-completions and responses parsing paths and adds regression coverage for the named tool-choice case. Fixes vllm-project#40147 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com>

QwertyJack · 2026-04-29T16:20:14Z

Correction to my previous note: the latest patch follows your inline suggestion. When forced tool choice sees content is None, it now returns no function calls ([]) instead of synthesizing an empty tool call/{} arguments.

DeepSeek parser remains unchanged, and the branch is rebased. @chaunceyjiang PTAL.

) ### What this PR does / why we need it? Backports the forced tool-choice `content=None` handling from vLLM Ascend PR #8400 for the vLLM 0.19.1 patch layer. Related issue and PR: - vLLM issue: vllm-project/vllm#40147 - vLLM PR: vllm-project/vllm#40148 - vLLM Ascend PR: #8400 Per the latest PR #40148 discussion, this patch does not synthesize an empty function call or empty `{}` arguments. When forced tool choice sees `content=None`, it returns an empty tool-call list and preserves normal forced tool-call behavior when content is present. ### Does this PR introduce _any_ user-facing change? Yes. Forced tool-choice requests no longer assert when reasoning extraction leaves `content=None`; they return no tool calls for that empty-content result instead. ### How was this patch tested? - `ruff format --check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `ruff check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `python -m py_compile vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py` - `PYTHONPATH=../vllm:. pytest -q --confcutdir=tests/ut/patch/platform tests/ut/patch/platform/test_patch_tool_choice_none_content.py` Also ran `bash format.sh ci`; it passed the available hooks but could not complete `shellcheck` because `shellcheck` is not installed in this environment. - vLLM version: v0.19.1 - vLLM main: vllm-project/vllm@d886c26 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com>

Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com>

chaunceyjiang

LGTM.

@QwertyJack I added an e2e test based on your work.

…lm-project#8833) ### What this PR does / why we need it? Backports the forced tool-choice `content=None` handling from vLLM Ascend PR vllm-project#8400 for the vLLM 0.19.1 patch layer. Related issue and PR: - vLLM issue: vllm-project/vllm#40147 - vLLM PR: vllm-project/vllm#40148 - vLLM Ascend PR: vllm-project#8400 Per the latest PR #40148 discussion, this patch does not synthesize an empty function call or empty `{}` arguments. When forced tool choice sees `content=None`, it returns an empty tool-call list and preserves normal forced tool-call behavior when content is present. ### Does this PR introduce _any_ user-facing change? Yes. Forced tool-choice requests no longer assert when reasoning extraction leaves `content=None`; they return no tool calls for that empty-content result instead. ### How was this patch tested? - `ruff format --check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `ruff check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `python -m py_compile vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py` - `PYTHONPATH=../vllm:. pytest -q --confcutdir=tests/ut/patch/platform tests/ut/patch/platform/test_patch_tool_choice_none_content.py` Also ran `bash format.sh ci`; it passed the available hooks but could not complete `shellcheck` because `shellcheck` is not installed in this environment. - vLLM version: v0.19.1 - vLLM main: vllm-project/vllm@d886c26 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com>

…lm-project#8833) ### What this PR does / why we need it? Backports the forced tool-choice `content=None` handling from vLLM Ascend PR vllm-project#8400 for the vLLM 0.19.1 patch layer. Related issue and PR: - vLLM issue: vllm-project/vllm#40147 - vLLM PR: vllm-project/vllm#40148 - vLLM Ascend PR: vllm-project#8400 Per the latest PR #40148 discussion, this patch does not synthesize an empty function call or empty `{}` arguments. When forced tool choice sees `content=None`, it returns an empty tool-call list and preserves normal forced tool-call behavior when content is present. ### Does this PR introduce _any_ user-facing change? Yes. Forced tool-choice requests no longer assert when reasoning extraction leaves `content=None`; they return no tool calls for that empty-content result instead. ### How was this patch tested? - `ruff format --check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `ruff check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `python -m py_compile vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py` - `PYTHONPATH=../vllm:. pytest -q --confcutdir=tests/ut/patch/platform tests/ut/patch/platform/test_patch_tool_choice_none_content.py` Also ran `bash format.sh ci`; it passed the available hooks but could not complete `shellcheck` because `shellcheck` is not installed in this environment. - vLLM version: v0.19.1 - vLLM main: vllm-project/vllm@d886c26 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: PiratePai <416932041@qq.com>

…ct#40148) Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: chaunceyjiang <chaunceyjiang@gmail.com> Signed-off-by: Ifta Khairul Alam Adil <ikaadil007@gmail.com>

…ct#40148) Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: chaunceyjiang <chaunceyjiang@gmail.com> Signed-off-by: Libin Tang <libin.tang@intel.com>

…lm-project#8833) ### What this PR does / why we need it? Backports the forced tool-choice `content=None` handling from vLLM Ascend PR vllm-project#8400 for the vLLM 0.19.1 patch layer. Related issue and PR: - vLLM issue: vllm-project/vllm#40147 - vLLM PR: vllm-project/vllm#40148 - vLLM Ascend PR: vllm-project#8400 Per the latest PR #40148 discussion, this patch does not synthesize an empty function call or empty `{}` arguments. When forced tool choice sees `content=None`, it returns an empty tool-call list and preserves normal forced tool-call behavior when content is present. ### Does this PR introduce _any_ user-facing change? Yes. Forced tool-choice requests no longer assert when reasoning extraction leaves `content=None`; they return no tool calls for that empty-content result instead. ### How was this patch tested? - `ruff format --check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `ruff check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `python -m py_compile vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py` - `PYTHONPATH=../vllm:. pytest -q --confcutdir=tests/ut/patch/platform tests/ut/patch/platform/test_patch_tool_choice_none_content.py` Also ran `bash format.sh ci`; it passed the available hooks but could not complete `shellcheck` because `shellcheck` is not installed in this environment. - vLLM version: v0.19.1 - vLLM main: vllm-project/vllm@d886c26 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: yangzhe-2026 <yangzhe@isrc.iscas.ac.cn>

…lm-project#8833) ### What this PR does / why we need it? Backports the forced tool-choice `content=None` handling from vLLM Ascend PR vllm-project#8400 for the vLLM 0.19.1 patch layer. Related issue and PR: - vLLM issue: vllm-project/vllm#40147 - vLLM PR: vllm-project/vllm#40148 - vLLM Ascend PR: vllm-project#8400 Per the latest PR #40148 discussion, this patch does not synthesize an empty function call or empty `{}` arguments. When forced tool choice sees `content=None`, it returns an empty tool-call list and preserves normal forced tool-call behavior when content is present. ### Does this PR introduce _any_ user-facing change? Yes. Forced tool-choice requests no longer assert when reasoning extraction leaves `content=None`; they return no tool calls for that empty-content result instead. ### How was this patch tested? - `ruff format --check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `ruff check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `python -m py_compile vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py` - `PYTHONPATH=../vllm:. pytest -q --confcutdir=tests/ut/patch/platform tests/ut/patch/platform/test_patch_tool_choice_none_content.py` Also ran `bash format.sh ci`; it passed the available hooks but could not complete `shellcheck` because `shellcheck` is not installed in this environment. - vLLM version: v0.19.1 - vLLM main: vllm-project/vllm@d886c26 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: ZhuQi-seu <zhuqi12@huawei.com>

…ct#40148) Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: chaunceyjiang <chaunceyjiang@gmail.com>

…lm-project#8833) ### What this PR does / why we need it? Backports the forced tool-choice `content=None` handling from vLLM Ascend PR vllm-project#8400 for the vLLM 0.19.1 patch layer. Related issue and PR: - vLLM issue: vllm-project/vllm#40147 - vLLM PR: vllm-project/vllm#40148 - vLLM Ascend PR: vllm-project#8400 Per the latest PR #40148 discussion, this patch does not synthesize an empty function call or empty `{}` arguments. When forced tool choice sees `content=None`, it returns an empty tool-call list and preserves normal forced tool-call behavior when content is present. ### Does this PR introduce _any_ user-facing change? Yes. Forced tool-choice requests no longer assert when reasoning extraction leaves `content=None`; they return no tool calls for that empty-content result instead. ### How was this patch tested? - `ruff format --check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `ruff check vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py vllm_ascend/patch/platform/__init__.py vllm_ascend/patch/__init__.py` - `python -m py_compile vllm_ascend/patch/platform/patch_tool_choice_none_content.py tests/ut/patch/platform/test_patch_tool_choice_none_content.py` - `PYTHONPATH=../vllm:. pytest -q --confcutdir=tests/ut/patch/platform tests/ut/patch/platform/test_patch_tool_choice_none_content.py` Also ran `bash format.sh ci`; it passed the available hooks but could not complete `shellcheck` because `shellcheck` is not installed in this environment. - vLLM version: v0.19.1 - vLLM main: vllm-project/vllm@d886c26 Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: nanxing <1014662416@qq.com>

…ct#40148) Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: chaunceyjiang <chaunceyjiang@gmail.com>

…pty content (vllm-project#8400) ### What this PR does / why we need it? This backports the forced-tool-choice `content=None` guard to the `releases/v0.18.0` compatibility layer. Upstream vLLM still has forced named tool-choice branches that assert `content is not None` after reasoning extraction. Some reasoning parsers can legally consume the full output and return `(reasoning, None)`, which makes the assert reachable and can surface as a server-side failure. This PR follows the same compatibility-patch pattern used by: - `7314bbe2` fix(platform): reimplement MiniMax usage accounting patch (vllm-project#7835) - `f83cb0e6` [Bugfix][Platform] Fix GLM47 tool-call finish backfill (vllm-project#7710) The patch is intentionally narrow: - normalize `content=None` to `""` only for forced named tool choice - patch both chat-completions and responses parser entry points - keep the rest of upstream behavior unchanged Upstream tracking: - issue: vllm-project/vllm#40147 - PR: vllm-project/vllm#40148 ### Does this PR introduce _any_ user-facing change? Yes. Forced named tool choice becomes robust when the reasoning parser returns no post-reasoning content, avoiding an internal assertion failure and emitting an empty-argument function call instead. ### How was this patch tested? Unit tests: ```bash pytest -sv tests/ut/patch/platform/test_patch_tool_choice_none_content.py \ tests/ut/patch/platform/test_patch_glm_tool_call_parser.py \ tests/ut/patch/platform/test_patch_minimax_usage_accounting.py ``` Result: 22 passed. --------- Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com>

…ct#40148) Signed-off-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com> Co-authored-by: QwertyJack <7554089+QwertyJack@users.noreply.github.com> Co-authored-by: chaunceyjiang <chaunceyjiang@gmail.com> Signed-off-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>

QwertyJack requested review from DarkLight1337, NickLucche, aarnphm, chaunceyjiang, robertgshaw2-redhat, russellb and sfeng33 as code owners April 17, 2026 13:17

claude Bot reviewed Apr 17, 2026

View reviewed changes

mergify Bot added frontend tool-calling labels Apr 17, 2026

github-project-automation Bot added this to Tool Calling Apr 17, 2026

gemini-code-assist Bot reviewed Apr 17, 2026

View reviewed changes

QwertyJack mentioned this pull request Apr 17, 2026

[releases/v0.18.0][Platform][BugFix] Guard forced tool choice with empty content vllm-project/vllm-ascend#8400

Merged

This was referenced Apr 21, 2026

[Bug]: Forced tool_choice crashes with AssertionError when reasoning_parser consumes all content #40528

Open

[Bugfix] Fix forced tool_choice crash when reasoning_parser consumes all content #40529

Open

chaunceyjiang self-assigned this Apr 28, 2026

mergify Bot added the needs-rebase label Apr 28, 2026

QwertyJack force-pushed the fix/tool-choice-content-none-assert branch from 2f88d21 to 5dc783e Compare April 28, 2026 10:54

QwertyJack requested a review from bbrowning as a code owner April 28, 2026 10:54

mergify Bot removed the needs-rebase label Apr 28, 2026

chaunceyjiang reviewed Apr 28, 2026

View reviewed changes

QwertyJack force-pushed the fix/tool-choice-content-none-assert branch from 5dc783e to 1184780 Compare April 28, 2026 12:35

mergify Bot added the deepseek Related to DeepSeek models label Apr 28, 2026

QwertyJack requested a review from chaunceyjiang April 29, 2026 13:19

chaunceyjiang reviewed Apr 29, 2026

View reviewed changes

Comment thread vllm/entrypoints/openai/engine/serving.py Outdated

QwertyJack force-pushed the fix/tool-choice-content-none-assert branch from 1554a8b to 1147f21 Compare April 29, 2026 16:18

QwertyJack mentioned this pull request Apr 30, 2026

[BugFix][Patch] Backport forced tool choice none-content handling vllm-project/vllm-ascend#8833

Merged

chaunceyjiang added 3 commits April 30, 2026 14:49

[Bugfix] Fix crash when tool_choice=named/forced exceeds max_tokens

ea7301d

Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com>

[Bugfix] Fix crash when tool_choice=named/forced exceeds max_tokens

af9ff27

Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com>

[Bugfix] Fix crash when tool_choice=named/forced exceeds max_tokens

a9b08da

Signed-off-by: chaunceyjiang <chaunceyjiang@gmail.com>

chaunceyjiang added the ready ONLY add when PR is ready to merge/full CI is needed label Apr 30, 2026

chaunceyjiang approved these changes Apr 30, 2026

View reviewed changes

chaunceyjiang enabled auto-merge (squash) April 30, 2026 07:01

chaunceyjiang added 2 commits April 30, 2026 20:08

Merge branch 'main' into fix/tool-choice-content-none-assert

65140ec

Merge branch 'main' into fix/tool-choice-content-none-assert

5eb9a67

chaunceyjiang merged commit 6467213 into vllm-project:main May 6, 2026
50 checks passed

github-project-automation Bot moved this to Done in Tool Calling May 6, 2026

QwertyJack deleted the fix/tool-choice-content-none-assert branch May 17, 2026 15:17

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(openai): tolerate empty content in forced tool choice#40148

fix(openai): tolerate empty content in forced tool choice#40148
chaunceyjiang merged 6 commits into
vllm-project:mainfrom
QwertyJack:fix/tool-choice-content-none-assert

QwertyJack commented Apr 17, 2026

Uh oh!

claude Bot left a comment

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

ywang96 commented Apr 21, 2026

Uh oh!

mergify Bot commented Apr 28, 2026

Uh oh!

chaunceyjiang commented Apr 28, 2026

Uh oh!

QwertyJack commented Apr 28, 2026

Uh oh!

chaunceyjiang Apr 28, 2026

Uh oh!

chaunceyjiang commented Apr 28, 2026

Uh oh!

Uh oh!

QwertyJack commented Apr 29, 2026

Uh oh!

chaunceyjiang left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

QwertyJack commented Apr 17, 2026

Summary

Changes

Testing

Uh oh!

claude Bot left a comment

Choose a reason for hiding this comment

Claude Code Review

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

ywang96 commented Apr 21, 2026

Uh oh!

mergify Bot commented Apr 28, 2026

Uh oh!

chaunceyjiang commented Apr 28, 2026

Uh oh!

QwertyJack commented Apr 28, 2026

Uh oh!

chaunceyjiang Apr 28, 2026

Choose a reason for hiding this comment

Uh oh!

chaunceyjiang commented Apr 28, 2026

Uh oh!

Uh oh!

QwertyJack commented Apr 29, 2026

Uh oh!

chaunceyjiang left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants