[ssbuffer](fix) adjust iter_args insertion position in whileOp - #1895
Open
m-everglow wants to merge 1 commit into
Open
[ssbuffer](fix) adjust iter_args insertion position in whileOp#1895m-everglow wants to merge 1 commit into
m-everglow wants to merge 1 commit into
Conversation
m-everglow
requested review from
KanuaK,
WuTYSFG and
hongziqi
as code owners
September 1, 2026 08:50
github-actions
Bot
added
compiler
m-everglow
force-pushed
the
htsu
branch
4 times, most recently
from
September 2, 2026 02:43
cafd56d to
b575e88
Compare
Skyminers
reviewed
Sep 2, 2026
Signed-off-by: m-everglow <2276518549@qq.com>
WuTYSFG
approved these changes
Sep 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
DynamicCVPipleline: adjust iter_args insertion position in whileOp
New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
I have run
pre-commit run --from-ref origin/main --to-ref HEAD.Select one of the following.
/testforlittests/unittestfor C++ tests/python/testfor end-to-end testsFILL THIS IN.Select one of the following.
littests.littests I have added follow these best practices,including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)