On 6/23/17 1:11 PM, Daniel Stone wrote:
Hi Quentin,
On 13 April 2017 at 20:15, Quentin Glidic
wrote:
When switching a state twice in a row, we were overwriting the old value
without setting it back, sending a wrong state to the client.
Now we update our requested state, then check if we need
Hi Quentin,
On 13 April 2017 at 20:15, Quentin Glidic
wrote:
> When switching a state twice in a row, we were overwriting the old value
> without setting it back, sending a wrong state to the client.
>
> Now we update our requested state, then check if we need to schedule a
> configure event, if
From: Quentin Glidic
When switching a state twice in a row, we were overwriting the old value
without setting it back, sending a wrong state to the client.
Now we update our requested state, then check if we need to schedule a
configure event, if we have one scheduled already or even if we can
c
