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
Describe the bug
When Nightscout is configured with CONNECT_SOURCE=linkup, the server crashes upon initial load of data from Libre Link Up. This is due to a bug in nightscout_connect which improperly handles data ingestion when there are no previous data points.
If last_known is null, the plugin crashes with the following error, causing a reboot loop on the container:
This issue is fixed in nightscout_connect by adding in appropriate checks to ensure that direct reference to an undefined var are not performed and thus prevents the plugin from crashing.
This does not fix the crash in Nightscout as a result of the plugin crashing.
Upon retrieving data from Link Up the plugin crashes
Expected behavior
Connect should retrieve the patient data from LinkUp, process it then send it to Nightscout
Screenshots
N/A
Your setup information
Nightscout 15.0.2
Freestyle Libre 3 + Libre Link up
Additional context
This bug was originally posted in nightscout/nightscout-connect#27, cross posting it here because the failure in the connect plugin causes Nightscout to crash and restart, which is indicative of an error handling issue.
The connect issue is fixed in nightscout/nightscout-connect#34
The text was updated successfully, but these errors were encountered:
Describe the bug
When Nightscout is configured with
CONNECT_SOURCE=linkup
, the server crashes upon initial load of data from Libre Link Up. This is due to a bug innightscout_connect
which improperly handles data ingestion when there are no previous data points.If last_known is null, the plugin crashes with the following error, causing a reboot loop on the container:
This issue is fixed in
nightscout_connect
by adding in appropriate checks to ensure that direct reference to an undefined var are not performed and thus prevents the plugin from crashing.This does not fix the crash in Nightscout as a result of the plugin crashing.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connect should retrieve the patient data from LinkUp, process it then send it to Nightscout
Screenshots
N/A
Your setup information
Additional context
This bug was originally posted in nightscout/nightscout-connect#27, cross posting it here because the failure in the connect plugin causes Nightscout to crash and restart, which is indicative of an error handling issue.
The connect issue is fixed in nightscout/nightscout-connect#34
The text was updated successfully, but these errors were encountered: