Endpoint 1.0/events dont comming message "instance-running"

[puivan]

Greetings to your team! Continuing the topic of events, I noticed another problem, but already related to tracking the status of the session. The fact is that messages come from the websocket at the time of session creation (instance) when the status changes to STARTED, the message comes like this: {
"type": "lifecycle",
"timestamp": "2024-09-25T07:26:02.585971312Z",
"metadata": {
"action": "instance-started",
        "source": "/1.0/instances/crprl3np0q7s01sfhfgg"
}
but when the status changes to RUNNING, the same message comes from the websocket {
"type": "lifecycle",
    "timestamp": "2024-09-25T07:26:02.585971312Z",
    "metadata": {
        "action": "instance-started",
        "source": "/1.0/instances/crprl3np0q7s01sfhfgg"
    }
 and then the question arises, isn't it an error? maybe a message should come here that the status is no longer STARTED but RUNNING? This problem can be solved by making an additional request to check the status, then the question arises what is the point of using a websocket at all?

[Simon Fels (morphis)]

Thanks for reporting!

Not reporting the "instance-running" event is a bug and will be fixed in a following release.

[puivan (puivan)]

Thanks for the answer! And what is the latest version in 1.24, which will be released on November 14th?

[Simon Fels (morphis)]

No, the bug is scheduled for 1.23.2 (see the set milestone above) which will be release on Oct 16, see https://documentation.ubuntu.com/anbox-cloud/en/latest/reference/release-notes/release-notes/

Once the fix is merged and available in 1.23/beta you can give it a try even before the official release.