ble-reticulum/migration
2026-05-18 15:03:18 -07:00
..
phase2 Confirmation Report on jp and zerodev1 2026-05-18 15:03:18 -07:00
preserved_runs Phase 2 Gate 2A plan and report 2026-05-18 14:44:25 -07:00
protocol_core Add Gate 2B BLE peer session manager native tests 2026-05-18 14:58:20 -07:00
reports Record Gate 2B native session manager status 2026-05-18 14:59:13 -07:00
scripts First phase success 2026-05-16 17:19:26 -07:00
sql Add Gate 2B BLE peer session manager native tests 2026-05-18 14:58:20 -07:00
tests Add Gate 2B BLE peer session manager native tests 2026-05-18 14:58:20 -07:00
.gitignore First phase success 2026-05-16 17:19:26 -07:00
ble_symbols_20260516_1429.txt safety, no data imported into sqlite yet 2026-05-16 15:46:53 -07:00
Codex_prompt_20250616_1449.md safety, no data imported into sqlite yet 2026-05-16 15:46:53 -07:00
Codex_prompt_State2A_20250518_1433.md Phase 2 Gate 2A plan and report 2026-05-18 14:44:25 -07:00
Codex_response_20260616_1514.md safety, no data imported into sqlite yet 2026-05-16 15:46:53 -07:00
Migration_Testing_Journal.md Phase 2 Gate 2A plan and report 2026-05-18 14:44:25 -07:00
pi_zero_command_clumps.txt safety 2026-05-17 04:59:38 -07:00
README.md Fixed 2 warnings issued, revised report 2026-05-16 17:51:16 -07:00
reticulum_info_20260516_1444.txt safety, no data imported into sqlite yet 2026-05-16 15:46:53 -07:00

This directory concerns the migration to C++ the ble-reticulum project.

Test environment note

The project pytest configuration expects pytest-asyncio. 2 warning had issued, I had to rem the --disable-warnings flag in pytest.ini for the warnings to appear, when they appeared is became obvious that the absence of pytest-asyncio was creating the problem.

FIX: Install in the active virtual environment:

python3 -m pip install pytest-asyncio

Equivalence test:

cd /usr/local/src/ble-reticulum
python3 -m pytest migration/tests/test_fragmentation_cpp_equivalence.py -vv