Some modules are never executed when errors persist

[dostuffthatmatters]

Here is the order of how the different modules are executed:

pyra/packages/core/main.py

Lines 99 to 105 in dd29bae

	mainloop_modules: list[Any] = [
	modules.measurement_conditions.MeasurementConditions(config),
	modules.enclosure_control.EnclosureControl(config),
	modules.sun_tracking.SunTracking(config),
	modules.opus_measurement.OpusMeasurement(config),
	modules.system_checks.SystemChecks(config),
	]

When one module raises an Exception, none of the modules after that will be executed. So if the enclosure or CamTracker has an error, the OPUS-module will never be executed (so OPUS will never be started or stopped accordingly).

Solution: Since modules 2 to 5 depend on 1 but not on each other, we could move the processing of any exception after all of them (2 to 5) have been executed. Then we would still toggle OPUS/CamTracker correctly and check for battery state etc. even when the enclosure has issues. The emailing logic (occurred, resolved) will not be affected.

[patrickjaigner]

@dostuffthatmatters thanks for the idea. I agree that this should improve the process.