Repo Added
|
Files
145
|
Badge
README BADGES
|
push
gitlab-ci
fix: parse artifact ID before validating payload size If a deployment fails before the artifact info is parsed, e.g. when a deployment is started but S3 is blocked by a firewall, the JSON state data describes an artifact with an empty payload-types list. If mender-update is subsequently restarted, the JSON state data unmarshaler would exit early and return invalid state data (empty deployment ID) triggering an assert in DeploymentClient::PushStatus. The client would never recover from this. Original-by: Fredrik Ellertsen <fredrik.ellertsen@disruptive-technologies.com> * https://github.com/mendersoftware/mender/pull/1635 Modified-by: Kristian Amlie <kristian.amlie@northern.tech> * Fix compile error due to declaration order. * Made same fix for loading v1 state data. * Adjusted changelog entry. Changelog: Fix error which could sometimes happen with restrictive firewalls, resulting in this output: ``` Programming error, should not happen: Assert `deployment_id != ""` ``` Ticket: MEN-7327 Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech> (cherry picked from commit 0321b33d3)
4 of 4 new or added lines in 1 file covered. (100.0%)
7077 of 8871 relevant lines covered (79.78%)
12331.59 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|
Builds | Branch | Commit | Type | Ran | Committer | Via | Coverage |
---|---|---|---|---|---|---|---|
1325231394 | pr_1638 | fix: parse artifact ID before validating payload size If a deployment fails before the artifact info is parsed, e.g. when a deployment is started but S3 is blocked by a firewall, the JSON state data describes an artifact with an empty payload-typ... | push | gitlab-ci |
79.78 |