Communication CFT Weekly [2026-01-12]

[LittleHuba]

Participants

@mikehaller
@JochenSatETAS
@bharatGoswami8
@darkwisebear
@NEOatNHNG
@mina-hamdi
@alexandruiulian10
@dasoho
@kalu-an
@SebastianGrob
@Abhishek2581
@arsibo
@lurtz
@sahithi-nukala
@Tejveerpratap2803
@LittleHuba

Agenda

1. Dependency of logging on message-passing (Raised by discussion in slack https://sdvworkinggroup.slack.com/archives/C08C0JATADP/p1767800408951309)
2. Quick peek at the last release
3. @dasoho : Open SOME/IP sepcification - Shall we add it to the feature documentation

#Minutes

to 1.

Original question by @pawelrutkaq raising this discussion

Hello. Currently we are seeing "strange" situation where score_logging will need to depend on score_communication due to message passing component. Is this intended long term, or shall this component be moved to score_baselibs ?

Background:

• Frontend does not depend on message_passing
• ONLY the DLT backend depends on message_passing
• Based on feedback from Raghavendra Maddikery this dependency is known and does not create problems in the dependency tree

Conclusion:

• message_passing is not only an abstraction of the OS. Hence, it is a communication library that should also reside in the communication repository.

to 2.

QNX workflows need fix for runs on PRs from forks
Please send ideas/documentation to @LittleHuba

Resources collected during the meeting:
https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/

LLVM coverage
@lurtz mentioned that it might not work to exclude code from the coverage report (based on knowledge from last year)

to 3.

• Currently the open specification does not contain SOME/IP-TP, E2E and TLV (though nobody is currently requesting the last one).
• Integrators will for now still have to add functionality that we do not provide in S-CORE due to our limitations
• We closely follow on this open standard and will make use of it as far as we can
• We should link the open specification in the feature documentation (https://github.com/eclipse-score/score/blob/main/docs/features/communication/some_ip_gateway/index.rst) (@dasoho)

WARNING

If you have a PR please do not add merge commits via "Update Branch"! Always use "Update with rebase"

[pawelrutkaq]

@LittleHuba, what's the problem with QNX workflow? There is already a workflow for QNX8 that is tackling the issue of forked PRs (access to secrets etc). Is this the problem mentioned here? (@dcalavrezo-qorix was working on it afaik)