Skip to content

Uninstall: remove every SuperTon data and cache location - #41

Merged
therahul-yo merged 1 commit into
mainfrom
uninstall-full-cleanup
Jun 11, 2026
Merged

Uninstall: remove every SuperTon data and cache location#41
therahul-yo merged 1 commit into
mainfrom
uninstall-full-cleanup

Conversation

@therahul-yo

Copy link
Copy Markdown
Owner

superton uninstall left several things behind:

  • chromadb cache (~/Library/Caches/chroma / ~/.cache/chroma) — the semantic backend downloads ONNX embedding models here, often the largest leftover
  • SuperTon cache dir (~/Library/Caches/superton)
  • default data dir when SUPERTON_HOME pointed elsewhere — only the env-var location was removed

New _data_paths() enumerates every location SuperTon may have written; the data stage and the pre-flight card now sweep/show all of them. Ollama model removal and the CLI orphan sweep were already correct.

Test plan

  • 223 tests pass (new test for _data_paths)
  • Manual: _data_paths lists home, default data dir, both cache dirs, deduped

🤖 Generated with Claude Code

superton uninstall only removed cfg.home, leaving the chromadb cache
(downloaded embedding models), SuperTon's cache dir, and — when
SUPERTON_HOME pointed elsewhere — the default data dir. The data stage
now sweeps every location SuperTon may have written.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
superton Building Building Preview Jun 11, 2026 7:07am

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@therahul-yo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 44 minutes and 6 seconds. Learn how PR review limits work.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d917f9bc-504a-49ba-a7d8-a479722d0a66

📥 Commits

Reviewing files that changed from the base of the PR and between 8335a46 and 349e7b4.

📒 Files selected for processing (2)
  • superton/cli.py
  • tests/test_cli.py

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@therahul-yo
therahul-yo merged commit f18a47f into main Jun 11, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant