mirror of
https://github.com/GNS3/gns3-server.git
synced 2026-10-12 13:35:31 +03:00
82015dcb5c
Every node lifecycle call (start/stop) emitted a "starting"/"stopping" node.updated notification on entry, and for the whole duration of the call asdict() masked the real status with the transitional one — every compute event forwarded in that window was re-emitted as a duplicate transitional status. Stop-all/start-all on a 13-node project pushed two transitional events per node before the final state. Clients that do not render these transitional statuses (the Web UI) showed nodes flickering through an unexpected suspended-looking state before reaching started/stopped. Remove the transitional notification and the status masking: clients see the real statuses again (started/stopped), from the forwarded compute events plus the controller-side confirmation. The wait option on the lifecycle routes, the strict stop error handling and wait_for_status() are unchanged.