feat: cog weights import/pull download progress

[anish-sahoo]

Summary

• show live Docker-style download progress while cog weights import warms the local weight store
• show live Docker-style download progress while cog weights pull populates a cold local cache
• add focused tests for import and pull progress events

Testing

• mise run fmt:go:fix
• go test ./pkg/cli
• go test ./pkg/model
• go test ./pkg/weights
• mise run lint:go

[ask-bonk]

LGTM

github run

[ask-bonk]

LGTM

github run

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds live download progress display during cog weights import by plumbing a progress callback through the weight builder and ingress pipeline, with a focused test verifying progress event generation.

I found one issue with the progress display logic.

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds live download progress display during cog weights import by plumbing a progress callback through the weight builder and ingress pipeline, with a focused test verifying progress event generation.

I found one issue with the progress display logic.

Posted a batch review with a suggestion to fix intermediate files not being marked as "Download complete" in pkg/cli/weights.go:175.

github run

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds live download progress display during cog weights import and cog weights pull by plumbing progress callbacks through the weight builder and ingress/pull pipeline, with focused tests verifying progress event generation.

I found two issues with the progress display logic.

[ask-bonk]

Posted a batch review on PR #3087 with two suggestions:

1. pkg/cli/weights.go:175 — Remove prog.Complete >= prog.Total so intermediate files show "Download complete" when they finish.
2. pkg/weights/pull.go:305-318 — Add throttling to pullProgressReader (matching progressReader's 250ms interval) to prevent console flooding on large files.

github run

[ask-bonk]

@anish-sahoo Bonk workflow was cancelled.

View workflow run · To retry, trigger Bonk again.

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds live download progress display during cog weights import and cog weights pull by plumbing progress callbacks through the weight builder and ingress/pull pipeline, with focused tests verifying progress event generation.

I found one remaining issue with the progress display logic.

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds live download progress display during cog weights import and cog weights pull by plumbing progress callbacks through the weight builder and ingress/pull pipeline, with focused tests verifying progress event generation.

I found one remaining issue with the progress display logic.

1. pkg/weights/pull.go:305-318 — pullProgressReader emits a progress event on every Read() call without throttling, while progressReader in pkg/model/packer.go uses a 250ms interval to avoid flooding the console. For large files this can mean thousands of progress events per file. Add the same throttling behavior for consistent UX (also add "time" to the imports):

type pullProgressReader struct {
	r            io.Reader
	complete     int64
	lastReported int64
	lastUpdate   time.Time
	interval     time.Duration
	fn           func(int64)
}

func (r *pullProgressReader) Read(p []byte) (int, error) {
	n, err := r.r.Read(p)
	if n > 0 {
		r.complete += int64(n)
		now := time.Now()
		interval := r.interval
		if interval == 0 {
			interval = 250 * time.Millisecond
		}
		if r.lastReported == 0 || now.Sub(r.lastUpdate) >= interval {
			r.lastReported = r.complete
			r.lastUpdate = now
			r.fn(r.complete)
		}
	}
	return n, err
}

Posted a batch review on PR #3087 with this suggestion.

github run

[ask-bonk]

I've reviewed the current state of PR #3087. Both previously identified issues have been addressed:

1. pkg/cli/weights.go:175 — Fixed to mark each file complete when prog.Done is set, without the cumulative progress check.
2. pkg/weights/pull.go — pullProgressReader now implements proper throttling with a 250ms default interval, matching progressReader in packer.go.

I've also verified the progress event plumbing through weight_builder.go, the pull command in weights_pull.go, and the focused tests in both packer_test.go and pull_test.go. Everything looks consistent and correct.

LGTM

github run