Repository navigation
[CP v2.16] Show the CHIP server Node ID once the server has started - #137
Conversation
…p#136) * Show the CHIP server Node ID once the server has started (#1193) The Node ID is regenerated when the chip server starts during suite setup, after the run is already executing, so the one-shot query at 'executing' printed a stale ID. Watch the backend instead and display the Node ID (and manual pairing code) whenever the server is started and the ID changes. * Treat only an explicit server_started=False as not started A backend that predates the server_started field omits it; defaulting to False would suppress the Node ID banner entirely (#1193). * Re-generated api classes * isort (cherry picked from commit ba40a92)
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
Cherry-pick of #136 (ba40a92) from
v2.16-cli-develop. Requires the matching backend PR (server_startedfield).The CLI now watches
/chip-server/infoand shows the Node ID and manual pairing code once the chip server has started, instead of a stale ID fetched atexecuting.The squash commit also includes the regenerated API client from #136: it drops the unused
utils_api(no/utilsendpoint in the backend) and updatesmodels.py. Applied cleanly;pytest tests/test_run: 431 passed.Refs #1193