maximilien / maximilien/weave-cli
feat: ingestion status dashboard (weave docs status)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 34
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Problem
During 4-8 hour image ingestion runs, there is no way to see what is happening.
Client0 wrote a separate polling script that runs doc-count queries and parses log files
to show progress.
Proposed Solution
New command `weave docs status`:
```bash
weave docs status --milvus-local
```
Output:
```
π Collection Status (milvus-local)
ββββββββββββββββββββββββββββββββββββ
Collection Docs Status Last Updated
AuctionListings 267 β
ok 2026-02-17 14:32
AuctionListings_OSS 267 β
ok 2026-02-17 14:45
AuctionImages 6591 β
ok 2026-02-17 19:22
AuctionImages_OSS 1423 π ... 2026-02-17 21:45 (in progress)
βοΈ Active ingestion: AuctionImages_OSS
File: 2023-catalogue.pdf [7/9 files]
Chunks: 1,234 created
Elapsed: 2h 14m
```
Live mode (`--watch`): refresh every 5 seconds.
Priority
P2 β v0.9.30 target (~5 hours)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing weave docs command and the Milvus collection and document query paths. Define how ingestion progress and timestamps can be obtained before implementing weave docs status, including --milvus-local and --watch. Done means the command reports collection status and active ingestion progress in the proposed format and refreshes live every five seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100