Help: How to generate wiki-only?

[yairEO]

Running repowise init runs the indexing again and it takes forever. my indexing is good, I don't need it. I only need to generate the wiki since I skipped that part originally when running the init command. I did not find how (to do it) in the docs page

[RaghavChamadiya]

You can generate the wiki without re-indexing:

repowise update --full should work

If you indexed with repowise ≥ 0.16.0, repowise init --resume also works, the new phase ledger skips the completed index/analysis phases and jumps straight to generation

[yairEO]

What if I want to resume with a different coverage percentage (for example I originally chose 30% and now I want 50%) and a different LLM?

[yairEO]

BTW, I just aborted the generation (with CTRL+C) and saw this error:

⠦ Generating pages... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1/985 0:11:38 $0.000

Aborted!
sys:1: RuntimeWarning: coroutine 'PerTypeGenerationMixin.generate_symbol_spotlight' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

I'm on v0.16.0

[RaghavChamadiya]

Both are supported on the resume path:

repowise init --resume --coverage 0.5 --provider <name> --model <id>

• Coverage: resume treats the vector store as the ground truth for what's already generated, so going 30% → 50% only generates the missing pages, nothing is redone.
• LLM: the --provider/--model overrides apply to the resumed run, but note that pages generated earlier are kept as-is, not regenerated. So you'll end up with a wiki where older pages came from the old model. If you want everything from the new model, run repowise update --full with the new provider instead.

On the RuntimeWarning after Ctrl+C, that's a benign cancellation artifact: queued page-generation coroutines that were never started don't get closed when the run aborts. Nothing is lost (completed pages are persisted incrementally, so --resume continues exactly where you stopped, your 1/985 page won't be regenerated). I'll clean up the warning in an upcoming release. Tracking it from this issue.