vhalReady callback in the streaming SDK is called too early
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Anbox Cloud |
Fix Released
|
Medium
|
Michele Lo Russo |
Bug Description
The vhalReady callback was being called right after initialising the AnboxVhalManager. However, at this point, we still have not received any prop configs from Anbox. These can arrive with an imperceptible delay, but in some cases they are received after many seconds, giving enough time to the consumer (e.g. the dashboard) to try to call methods like getPropConfigs or getAllPropConfigs - thinking that "VHAL is ready" - and receiving an empty array response.
Steps to reproduce:
1. Go to the demo server page for the PR that introduces the usage of the new vhalReady callback: https:/
2. Join an AAOS session.
3. As soon as the VHAL panel opens, and before the stream loads, click on the "All VHAL properties" button in the panel.
4. See that the the list of received VHAL prop configs is empty. Before, the UI used to freeze (as shown in the attached screen captures), but this was caused by an uncontrolled rerendering loop that could be fixed, and is technically not strictly related to the issue above.
description: | updated |
Changed in anbox-cloud: | |
assignee: | nobody → Michele Lo Russo (lorumic) |
status: | Triaged → In Progress |
summary: |
- Dashboard: streaming page freezes due to never-returning VHAL getters in - the streaming SDK + vhalReady callback in the streaming SDK is called too early |
Changed in anbox-cloud: | |
status: | In Progress → Fix Committed |
Changed in anbox-cloud: | |
status: | Fix Committed → Fix Released |
Related to https:/ /bugs.launchpad .net/anbox- cloud/+ bug/2060532