In cc13x2x7_26x2x7, LogEvent seems to emanate from a thread other than the CHIP task.

[yunhanw-google]

I think cc13x2x7_26x2x7's main.cpp contains a call to LogEvent that seems to emanate from a thread other than the CHIP task.

Might want to file an issue on that.

Originally posted by @mrjerryjohns in #19285 (review)

[yunhanw-google]

@andreilitvin who is taking care of cc13x2x7_26x2x7?

[andy31415]

@andreilitvin who is taking care of cc13x2x7_26x2x7?

@srickardti maybe based on commit logs?

[srickardti]

@yunhanw-google can you point me to the offending code? The only reference to logging in our main.cpp files is a commented out platform log because the UART driver isn't up until the kernel is started.

In our examples we usually use a macro to call our platform logging function. Is there a better way to consolidate logging?

[bzbarsky-apple]

connectedhomeip % git grep -n LogEvent | grep cc13
examples/pump-app/cc13x2x7_26x2x7/main/AppTask.cpp:621:        if (CHIP_NO_ERROR != LogEvent(event, endpoint, eventNumber))

[bzbarsky-apple]

This is not about "logging". This is about Matter events.

[ReneJosefsen]

This is an old section of code used for demonstration purposes. Since events are not going to make it for 1.0 I would think the easiest solution is to just remove the code that triggers the LogEvent.

If that is acceptable, I can do a PR to fix this.

[bzbarsky-apple]

In what sense are "events not going to make it for 1.0"?

[ReneJosefsen]

I assumed that events in general was deferred for now, but there might be something I missed?

[bzbarsky-apple]

Events in general are implemented and tested.

[andy31415]

Fixed by 19379