Mark Haslinghuis


@chmelevskij is there a way to mark these sonar issues as informational instead of failing the analysis (seems sonar is tightening the screws) 

Fixed (https://github.com/betaflight/betaflight-configurator/issues/2894#issuecomment-1107523357)

Do not want to make it to complicated. Thinking about it perhaps we should have a second message - but requires keeping state. 1. At startup when no signal data...

Rebased on master

Please check build: https://github.com/betaflight/betaflight-configurator/pull/3511

Also might be relevant: https://github.com/betaflight/betaflight-configurator/pull/3512 as code 37 is `MSP_SET_FEATURE_CONFIG`

As it works on Linux this issue will be hard to debug without access to an Apple M2 16" MBP.

@robhaswell did you try https://github.com/betaflight/betaflight-configurator/pull/3695 ???

In serial_backend it uses 1.46 for testing.