Skip to content

fix(cd): uv sync must include serve extra (torch/faiss) #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andylizf merged 1 commit into from
Jun 2, 2026
Merged

fix(cd): uv sync must include serve extra (torch/faiss) #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions deploy/deploy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,13 @@ say "changed: $(echo "$CHANGED" | tr '\n' ' ')"

changed() { echo "$CHANGED" | grep -qE "$1"; }

# 1. Python deps
# 1. Python deps. MUST include the extras the box runs (the search API needs the
# `serve` extra: torch, transformers, faiss-cpu). A bare `uv sync` installs only
# the light core and would UNINSTALL torch/faiss, breaking the serves on their
# next restart. `all` = embed+serve+index (no gpu — there's no CUDA here).
if changed '^uv\.lock$'; then
say "uv.lock changed -> uv sync"
uv sync >>"$LOG" 2>&1 || say "WARN: uv sync failed"
say "uv.lock changed -> uv sync --extra all"
uv sync --extra all >>"$LOG" 2>&1 || say "WARN: uv sync failed"
fi

# 2. Agent backend — cheap restart, safe to automate.
Expand Down
Loading