Release v1.3.2

Author: jayantjn

.github/template/fwe-build/action.yml

@@ -28,25 +28,56 @@ runs:
         # prettier-ignore
         key: ${{ inputs.dist-name }}-${{ inputs.build-arch }}-${{ hashFiles('tools/install-deps-*.sh') }}
 
-    - name: install-deps
+    - name: restore-cache-deps
+      # Explicitly checking against true as the cache-hit output is a string value : "true", "false"
+      # or "". According to GitHub documentation : https://github.com/marketplace/actions/cache#outputs,
+      # it returns 'true' only on an exact primary key match, 'false' when using fallback restore-keys, and an
+      # empty string when no cache exists at all. In the current workflow configuration, cache-hit output would
+      # either return a "" when the cache is not available or a "true" if there is an exact key match.
+      if: steps.cache-deps.outputs.cache-hit == 'true'
       shell: bash
       run: |
+        echo "Cache found! Restoring cached dependencies..."
         IFS=":"
         CACHE_PATHS=${{ inputs.cache-paths }}
-        if [ -d cache ]; then
-          for P in ${CACHE_PATHS}; do
-            sudo mkdir -p `dirname ${P}`
-            sudo cp -r cache${P} ${P}
-          done
-        fi
-        sudo ./tools/install-deps-${{ inputs.build-arch }}.sh ${{ inputs.extra-options }}
-        if [ ! -d cache ]; then
-          for P in ${CACHE_PATHS}; do
-            mkdir -p cache`dirname ${P}`
-            cp -r ${P} cache${P}
-          done
+        for P in ${CACHE_PATHS}; do
+          sudo mkdir -p `dirname ${P}`
+          sudo cp -r cache${P} ${P}
+        done
+
+    - name: install-deps
+      shell: bash
+      run: |
+        # Add --use-cache flag if cache hit
+        EXTRA_OPTIONS="${{ inputs.extra-options }}"
+        # Explicitly checking against true as the cache-hit output is a string value : "true", "false" or ""
+        if [[ "${{ steps.cache-deps.outputs.cache-hit }}" == 'true' ]]; then
+          echo "Using cached dependencies, adding --use-cache flag"
+          EXTRA_OPTIONS="${EXTRA_OPTIONS} --use-cache"
+        else
+          echo "No cache hit, installing dependencies from scratch"
         fi
 
+        echo "Running installation with options: ${EXTRA_OPTIONS}"
+        sudo ./tools/install-deps-${{ inputs.build-arch }}.sh ${EXTRA_OPTIONS}
+
+    - name: create-cache
+      # Explicitly checking against "" as the cache-hit output is a string value : "true", "false"
+      # or "". According to GitHub documentation : https://github.com/marketplace/actions/cache#outputs,
+      # it returns 'true' only on an exact primary key match, 'false' when using fallback restore-keys, and an
+      # empty string when no cache exists at all. In the current workflow configuration, cache-hit output would
+      # either return a "" when the cache is not available or a "true" if there is an exact key match.
+      if: steps.cache-deps.outputs.cache-hit != 'true'
+      shell: bash
+      run: |
+        echo "Creating cache for future runs..."
+        IFS=":"
+        CACHE_PATHS=${{ inputs.cache-paths }}
+        for P in ${CACHE_PATHS}; do
+          sudo mkdir -p "$(dirname "cache${P}")"
+          sudo cp -r "${P}" "cache${P}"
+        done
+
     - name: build
       shell: bash
       run: |

.github/workflows/ci.yml

@@ -40,7 +40,7 @@ jobs:
           extra-options:
             "--with-someip-support --with-lks-support --with-greengrassv2-support
             --with-custom-function-examples --with-store-and-forward-support --with-uds-dtc-example
-            --with-micropython-support"
+            --with-micropython-support --prefix /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge"
           cache-paths: /usr/local/x86_64-linux-gnu
           dist-files: build/aws-iot-fleetwise-edge:.
@@ -56,7 +56,7 @@ jobs:
           extra-options:
             "--with-greengrassv2-support --with-someip-support --with-lks-support
             --with-custom-function-examples --with-store-and-forward-support --with-uds-dtc-example
-            --with-micropython-support"
+            --with-micropython-support --native-prefix /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge"
           cache-paths: /usr/local/aarch64-linux-gnu:/usr/local/x86_64-linux-gnu
           dist-files: build/aws-iot-fleetwise-edge:.
@@ -72,7 +72,8 @@ jobs:
           extra-options:
             "--with-greengrassv2-support --with-someip-support --with-lks-support
             --with-iwave-gps-support --with-custom-function-examples
-            --with-store-and-forward-support --with-uds-dtc-example --with-micropython-support"
+            --with-store-and-forward-support --with-uds-dtc-example --with-micropython-support
+            --native-prefix /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge"
           cache-paths: /usr/local/arm-linux-gnueabihf:/usr/local/x86_64-linux-gnu
           dist-files: build/aws-iot-fleetwise-edge:.
@@ -88,7 +89,7 @@ jobs:
           extra-options:
             "--with-greengrassv2-support --with-ros2-support --with-someip-support
             --with-lks-support --with-custom-function-examples --with-store-and-forward-support
-            --with-uds-dtc-example --with-micropython-support"
+            --with-uds-dtc-example --with-micropython-support --prefix /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge-ros2"
           cache-paths: /usr/local/x86_64-linux-gnu:/opt/ros
           dist-files: build/iotfleetwise/aws-iot-fleetwise-edge:.
@@ -104,7 +105,8 @@ jobs:
           extra-options:
             "--with-greengrassv2-support --with-ros2-support --with-someip-support
             --with-lks-support --with-custom-function-examples --with-store-and-forward-support
-            --with-uds-dtc-example --with-micropython-support"
+            --with-uds-dtc-example --with-micropython-support --native-prefix
+            /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge-ros2"
           cache-paths: /usr/local/aarch64-linux-gnu:/usr/local/x86_64-linux-gnu:/opt/ros
           dist-files: build/iotfleetwise/aws-iot-fleetwise-edge:.
@@ -120,7 +122,8 @@ jobs:
           extra-options:
             "--with-greengrassv2-support --with-ros2-support --with-someip-support
             --with-lks-support --with-custom-function-examples --with-store-and-forward-support
-            --with-uds-dtc-example --with-micropython-support"
+            --with-uds-dtc-example --with-micropython-support --native-prefix
+            /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge-ros2"
           cache-paths: /usr/local/arm-linux-gnueabihf:/usr/local/x86_64-linux-gnu:/opt/ros
           dist-files: build/iotfleetwise/aws-iot-fleetwise-edge:.
@@ -133,7 +136,9 @@ jobs:
         with:
           build-arch: "cross-android"
           upload-arch: "android"
-          extra-options: "--with-lks-support --with-custom-function-examples"
+          extra-options:
+            "--with-lks-support --with-custom-function-examples --native-prefix
+            /usr/local/x86_64-linux-gnu"
           dist-name: "aws-iot-fleetwise-edge"
           cache-paths: /usr/local/x86_64-linux-android:/usr/local/aarch64-linux-android:/usr/local/armv7a-linux-androideabi:/usr/local/x86_64-linux-gnu
           dist-files:

CHANGELOG.md

@@ -1,5 +1,21 @@
 # Change Log
 
+## v1.3.2 (2025-06-24)
+
+Bug fixes:
+
+- Fixed race conditions in `OBDOverCANModule`, `DataSenderIonWriter`,
+  `CollectionInspectionWorkerThread` and `CANDataSource` found by coverity 2024.3.1.
+
+Improvements:
+
+- Refactored telemetry data serialization to ensure Store and Forward uses the same payload size
+  optimizations as regular telemetry data.
+- Updated the default dependency installation prefix to `/usr/local`, enabling CMake to locate
+  dependencies using its standard search paths without requiring explicit `CMAKE_PREFIX_PATH`
+  argument.
+- Fixed various Coverity regressions.
+
 ## v1.3.1 (2025-04-25)
 
 Bug fixes:

CMakeLists.txt

@@ -2,7 +2,7 @@
 
 cmake_minimum_required(VERSION 3.10.2)
 
-project(iotfleetwise VERSION 1.3.1)
+project(iotfleetwise VERSION 1.3.2)
 
 # FWE uses C++14 for compatibility reasons with Automotive middlewares (Adaptive AUTOSAR, ROS2)
 # Note: When built with FWE_FEATURE_ROS2, colcon will override these settings

docs/dev-guide/store-and-forward-dev-guide.md

@@ -185,7 +185,7 @@ Install the dependencies for FWE:
 
 ```bash
 cd ~/aws-iot-fleetwise-edge &&
-sudo -H ./tools/install-deps-native.sh --with-store-and-forward-support --prefix /usr/local &&
+sudo -H ./tools/install-deps-native.sh --with-store-and-forward-support &&
 sudo ldconfig
 ```
 

docs/dev-guide/vision-system-data/vision-system-data-demo.ipynb

@@ -363,7 +363,7 @@
    "outputs": [],
    "source": [
     "# cd ~/aws-iot-fleetwise-edge\n",
-    "# sudo -H ./tools/install-deps-native.sh --with-ros2-support --prefix /usr/local\n",
+    "# sudo -H ./tools/install-deps-native.sh --with-ros2-support\n",
     "# sudo ldconfig"
    ]
   },

examples/README.md

@@ -68,7 +68,7 @@ launch an AWS EC2 Graviton (arm64) instance. Pricing for EC2 can be found,
 
    ```bash
    cd ~/aws-iot-fleetwise-edge \
-   && ./tools/install-deps-native.sh \
+   && sudo ./tools/install-deps-native.sh \
      --with-someip-support
    ```
 

examples/custom_function/CustomFunctionSin.cpp

@@ -1,4 +1,3 @@
-
 // Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
 // SPDX-License-Identifier: Apache-2.0
 

examples/custom_function/CustomFunctionSin.h

@@ -1,4 +1,3 @@
-
 // Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
 // SPDX-License-Identifier: Apache-2.0
 

examples/network_agnostic_actuator_commands/README.md

@@ -135,7 +135,7 @@ cd ~/aws-iot-fleetwise-edge/examples/network_agnostic_actuator_commands \
    {
      "executionId": "<COMMAND_EXECUTION_ID>",
      "commandArn": "arn:aws:iot:us-east-1:<ACCOUNT_ID>:command/activateAC",
-     "targetArn": "arn:aws:iot:us-east-1:<ACCOUNT_ID>:thing/fwe-example-network-agnostic-actuator-commands
+     "targetArn": "arn:aws:iot:us-east-1:<ACCOUNT_ID>:thing/fwe-example-network-agnostic-actuator-commands",
      "status": "SUCCEEDED",
      "statusReason": {
        "reasonCode": "4660",