fix(vault-sync): validate pairing device IDs#333
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
| Metric | Count |
|---|---|
| ✅ Passed | 108 |
| ❌ Failed | 22 |
| 📊 Total | 130 |
📊 View Reports
GitHub Pages (Live Reports):
Download Artifacts:
- robot-test-reports-html-no-api - HTML reports
- robot-test-results-xml-no-api - XML output
Summary
History
The vault-sync implementation is already committed and present on
dev. The macOS client and server broker landed through the June vault-sync commits included in merged PR #332. This is a small hardening follow-up discovered while reviewing that code.Testing
uv run --group test pytest tests/test_vault_sync_routes.pyuv run black --check src/advanced_omi_backend/models/vault_sync.py src/advanced_omi_backend/routers/modules/vault_sync_routes.py tests/test_vault_sync_routes.pyuv run isort --check-only src/advanced_omi_backend/models/vault_sync.py src/advanced_omi_backend/routers/modules/vault_sync_routes.py tests/test_vault_sync_routes.py