Release Notes

v1.1

None.

None.

Resolved Issues:

Resolved the transient timing issue observed during the processing of Stream Start Message by cam-service where a timeout causes an unrecoverable error in cam-service, the issue is reported in known issue.

Known Issues

When cam-service is deployed as a Zephyr application (CAM Integration with Kronos), a transient timing issue is observed after a timeout (either stream state or temporal faults). In this case, the timeout causes an unrecoverable error in cam-service with the following error string:
```
<err> pthread_mutex: Attempt to relock non-recursive mutex
```
This issue is only seen on specific hardware and in a small subset of cases.

Implementation of Critical Application Monitoring (CAM) as described in Overview.

When cam-service is deployed as a Zephyr application (CAM Integration with Kronos), a transient timing issue is observed after a timeout (either stream state or temporal faults). In this case, the timeout causes an unrecoverable error in cam-service with the following error string:
```
<err> pthread_mutex: Attempt to relock non-recursive mutex
```
This issue is only seen on specific hardware and in a small subset of cases.
When cam-service is deployed as a Linux or Zephyr application (CAM Integration with Kronos), a transient timing issue is observed during the processing of Stream Start Message by cam-service. In this case, the timeout causes an unrecoverable error in cam-service with the following error string:
```
ERROR: Stream state timeout error:
ERROR: stream_name: CAM STREAM 1
ERROR: stream_uuid: 84085ddc-bc10-11ed-9a44-7ef9696e0001
ERROR: error: state start to event timeout
```
This issue is only seen in a small subset of cases.