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
We need to show a notification that a firmware update is needed for probes that report:
an older node version than the current target,
or an older firmware version than the current target.
The reported node.js version is already stored in the DB, the target node.js version can be set via ENV. The reported firmware version is sent by the probes here but we don't read/store it yet, that needs to be added. The target version can again be set via ENV here.
When either of the versions is lower than the target, show the probe's status as yellow with the description "Ready (outdated)"
In #56, we'll also add a message with an explanation.
Note: We're tracking node and FW versions independently because since FW v2.0, the HW probes can self-update their stored containers.
The text was updated successfully, but these errors were encountered:
Continuation of jsdelivr/globalping-probe#171 as we can't auto update the HW probes.
We need to show a notification that a firmware update is needed for probes that report:
The reported node.js version is already stored in the DB, the target node.js version can be set via ENV. The reported firmware version is sent by the probes here but we don't read/store it yet, that needs to be added. The target version can again be set via ENV here.
When either of the versions is lower than the target, show the probe's status as yellow with the description "Ready (outdated)"
In #56, we'll also add a message with an explanation.
Note: We're tracking node and FW versions independently because since FW v2.0, the HW probes can self-update their stored containers.
The text was updated successfully, but these errors were encountered: