tiennm99 fafeab4750 feat: report progress while reading a chat and listing a remote ...

Both phases ran for minutes printing nothing between their opening line and
their result, so a working run looked exactly like a hung one — which is how it
was reported.

The message counter lives in Walk rather than in the caller's loop because most
of a chat is not media: text-only and service messages are filtered out inside
the walk, so a caller counting yielded items still sees nothing while crossing a
long stretch of conversation.

Cadence follows the existing reporter: a terminal redraws one line, a redirected
run gets a periodic one, since ANSI redraws are what turned the shell pipeline's
captured logs into megabytes of control characters.

2026-09-06 21:05:59 +07:00

..

fs_test.go

fix: detect truncated uploads, and stop reporting unreachable work as retryable

2026-09-06 20:44:08 +07:00

fs.go

fix: detect truncated uploads, and stop reporting unreachable work as retryable

2026-09-06 20:44:08 +07:00

index_env_test.go

feat: report progress while reading a chat and listing a remote

2026-09-06 21:05:59 +07:00

index_test.go

feat: report progress while reading a chat and listing a remote

2026-09-06 21:05:59 +07:00

index.go

feat: report progress while reading a chat and listing a remote

2026-09-06 21:05:59 +07:00