Per review feedback on #53997 from @teknium1: the flag was set True on failed device_id resolution but never reset, so a same-adapter reconnect that successfully resolves a real device_id would keep skipping server-side key verification indefinitely. Reset now happens at the top of connect(), before resolution runs, so every connect() attempt starts clean. A repeat failure re-sets the flag (unchanged behavior); a recovery correctly clears it. Adds TestDeviceIdRecoveryOnReconnect to cover the transition. |
||
|---|---|---|
| .. | ||
| browser | ||
| context_engine | ||
| cron_providers | ||
| dashboard_auth | ||
| disk-cleanup | ||
| google_meet | ||
| hermes-achievements | ||
| image_gen | ||
| kanban | ||
| memory | ||
| model-providers | ||
| observability | ||
| platforms | ||
| security-guidance | ||
| spotify | ||
| teams_pipeline | ||
| video_gen | ||
| web | ||
| __init__.py | ||
| plugin_utils.py | ||