Skip to content

ProgressBar: Prevent premature completion and warnings #4272

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

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

jufrantz
Copy link
Contributor

@jufrantz jufrantz commented Jul 21, 2025

When ProgressBarLoopScope requested nbLoopSteps exceeded maxStepsForLoops, floor division could cause loopAdvance to emit less steps than maxStepsForLoops, the progression could stop too early and warn “did not advance progress bar correct number of steps".

Replaces the division with integer accumulator ensuring it ends as expected.

Also silence unnecessary warning messages in batch mode.

Julien Frantz added 2 commits July 21, 2025 11:07
When `nbLoopSteps` exceeded `maxStepsForLoops`, floor division could cause
`loopAdvance` to emit less steps than `maxStepsForLoops`, the progression could
stop too early and warn “did not advance progress bar correct number of steps".

Replaces the division with integer accumulator ensuring it ends as expected.

Also safely guards against negative `nbLoopSteps`.
MComputation::progress may return 0 when no UI is available, causing
unnecessary warning messages in batch mode.
@seando-adsk seando-adsk added the workflows Related to in-context workflows label Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflows Related to in-context workflows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants