ITS/MFT decoder sends vector with certain errors details

[shahor02]

An output vectoro2::itsmft::ErrorMessage is added with information about ChipStat::RepeatingPixel error details (at the moment, other errors may be added). Each element of ErrorMessage is assigned as:
errMsg.id = chipID
errMsg.errType = ChipStat::RepeatingPixel (at the moment) errMsg.errInfo0 = row
errMsg.errInfo1 = col

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1

[alibuild]

Error while checking build/O2/fullCI for a0a01cc at 2025-01-02 13:15:

## sw/BUILD/O2-latest/log
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'


## sw/BUILD/O2Physics-latest/log
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:


## sw/BUILD/O2-full-system-test-latest/log
Detected critical problem in logfile reco_NOGPU.log
reco_NOGPU.log:[34911:calib-phos-l1phase]: [12:15:35][ERROR] Exception while running: Fatal error. Rethrowing.
reco_NOGPU.log-[34911:calib-phos-l1phase]: [12:15:35][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-phos-calib-workflow, device shutting down. Reason: Fatal error
[34911:calib-phos-l1phase]: [12:15:35][ERROR] Requested resource does not exist: http://alice-ccdb.cern.ch//PHS/Calib/BadMap/1735820135419/
[34911:calib-phos-l1phase]: [12:15:35][FATAL] Got nullptr from CCDB for path PHS/Calib/BadMap and timestamp 1735820135419
[34911:calib-phos-l1phase]: [12:15:35][ERROR] Exception while running: Fatal error. Rethrowing.
[34911:calib-phos-l1phase]: [12:15:35][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-phos-calib-workflow, device shutting down. Reason: Fatal error
[ERROR] Workflow crashed - PID 34911 (calib-phos-l1phase) did not exit correctly however it's not clear why. Exit code forced to 128.


## sw/BUILD/o2checkcode-latest/log
--
========== List of errors found ==========
++ GRERR=0
++ grep -v clang-diagnostic-error error-log.txt
++ grep ' error:'
++ GRERR=1
++ [[ 1 == 0 ]]
++ mkdir -p /sw/INSTALLROOT/c03d0402e07a35bf5e047c75224ee0bc85ed8a80/slc8_x86-64/o2checkcode/1.0-local172/etc/modulefiles
++ cat
--

Full log here.

[iravasen]

Hi @shahor02, thanks a lot! This looks fine to me. I will not be able to test it immediately but at some point this feature will be used in the ITS digital scan.