You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With lua reading a channel by name and a different task creating a new channel (e.g. via API and timing/scoring) - a collision may occur and firmware crash if the list of channels changes (via API) when lua is attempting to get a channel by name.
We probably need to add a mutex to protect reading and creating virtual channels.
The text was updated successfully, but these errors were encountered:
It seems that a mutex (lock) could be created in sampleRecord.c, protecting access to init_sample_buffer or (higher up the call stack) and get_channel_value_by_name. This will prevent issues of the sample record being changed while it is being scanned for the current channel value.
With lua reading a channel by name and a different task creating a new channel (e.g. via API and timing/scoring) - a collision may occur and firmware crash if the list of channels changes (via API) when lua is attempting to get a channel by name.
We probably need to add a mutex to protect reading and creating virtual channels.
The text was updated successfully, but these errors were encountered: