Repository navigation
Backend requirements '-r ../requirements.txt' unresolvable on deploy + stripped by filter (root deps may be uninstalled) #11135
Description
Activity
- added a commit that references this issue
on Jul 7, 2026 Closed — merged via #11237. Backend
post_sync_cmdnow rewrites-r ../requirements.txt→{BASE}/code_source/requirements.txt(was stripped by the grep filter, same as the #11117-chandling it sits next to), so the ~23 root runtime deps (paramiko, asyncssh, pypdf, python-docx/pptx, openpyxl, protobuf…) install on deploy. Verified the exact grep|sed pipeline output; +1 regression test (17 pass). Now that #11132 (upsert seeding) is merged, this correction reaches already-seeded SLM DBs on next sync.
Problem
autobot-backend/requirements.txt:60is-r ../requirements.txt(repo-root, ~56 deps). On deploy/opt/autobot/requirements.txtdoes not exist (onlyautobot-backend/is synced, not its sibling — same class as #11117), and the ansible/post_sync filter strips^-rlines, so those root deps are not installed via the code-sync/ansible dep path. The backend runs today only because the venv was populated earlier / overlap with backend reqs.Investigate + fix
Confirm whether the ~56 root requirements are actually needed at runtime; if so, either sync the root requirements.txt to the resolvable sibling path (like the #11117 constraints fix) or install it explicitly. Refs #11117, #10524, #10016 (member 4).