feat: Add :progress_bar_step config option

[georgeguimaraes]

The progress bar updates on every network chunk during downloads. This floods CI logs because the escape codes for in-place updates don't work there, so each update ends up on a new line.

Added a :progress_bar_step config option that limits updates to percentage boundaries:

# Update every 10%
config :bumblebee, :progress_bar_step, 10

Default is nil (current behavior). Setting it to 10 gives you ~10 lines of output instead of hundreds.

[Copilot]

Pull request overview

This PR adds a :progress_bar_step configuration option to reduce CI log flooding during model downloads. Instead of updating the progress bar on every network chunk (which creates hundreds of lines in CI logs where escape codes don't work), progress updates can now be limited to percentage boundaries.

Key changes:

• Added :progress_bar_step config option (default: nil for current behavior)
• Modified download progress tracking to include last_percent state
• Implemented stepped progress rendering logic to only update at configured intervals

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
lib/bumblebee/utils.ex	Added progress_bar_step/0 function to retrieve the config value with type spec and documentation
lib/bumblebee/utils/http.ex	Updated download state to track last_percent and added maybe_render_progress/2 function to conditionally render progress based on step configuration
README.md	Added documentation and examples for the new progress bar configuration options

Comments suppressed due to low confidence (1)

lib/bumblebee/utils/http.ex:102

• When using a step-based update, the progress bar may not show 100% completion. For example, with step = 10, if the last rendered update is at 92% (say last_percent = 92 because it jumped from 89%), then reaching 100% won't trigger a render since 100 >= 92 + 10 evaluates to 100 >= 102, which is false.

Consider either: (1) adding a final progress bar render in this handler when step is configured to always show 100% completion, or (2) using the boundary-crossing logic suggested for line 114, which would naturally handle this case by checking if div(100, 10) > div(92, 10) (i.e., 10 > 9, which is true).

      {:error, error} ->
        :httpc.cancel_request(state.request_id, :bumblebee)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jonatanklosko]

It may be reasonable to make the default 1 or 0.5 to limit the IO, it shouldn't make much difference UX wise. Arguably if we make it 1, we don't necessarily need it to be configurable, since that should be fine on CI, but either works for me.

[georgeguimaraes]

default is now 1