Adding error recording when no active event in pipeline

[Ricardo-1894]

Description

This PR:

1. Adding error recording when no active event to pipeline
2. Adding test
3. Related to issue #446

Types of Changes

Put an x in the boxes that apply

• [x] Feature (non-breaking change which adds functionality)
• [ ] Bug Fix (non-breaking change that fixes an issue)
• [ ] Breaking Change (feature/fix that causes existing features to not work as expected)
• [ ] Documentation

Checklist

• [x] I have read the [contribute]contributing doc
• [x] Classes, scripts, and environment variables follow existing naming convention
• [x] Lint and Unit tests pass locally
• [ ] New features on hardware have been tested on a local Raspberry Pi
• [ ] Mention new programs/binaries if any must be installed along with this change
• [ ] Mention new environment variables if any have been added to hardware/env file
• [x] Test coverage should not drop more than 3%
• [ ] Any new required python modules are added to the requirements.txt

[jackxujh]

It seems the PR currently handles the situation when there is not active event. It may be better if the title and description reflect that. Because otherwise, people might expect it to handle situations like, the sensor is not valid, etc.

[Ricardo-1894]

It seems the PR currently handles the situation when there is not active event. It may be better if the title and description reflect that. Because otherwise, people might expect it to handle situations like, the sensor is not valid, etc.

Good point, I have updated the description