Communication FT Weekly [2026-09-07]

[LittleHuba]

Participants

@JochenSatETAS
@Thomas-Mikhael
@bharatGoswami8
@Rutuja-Patil-Bosch
@basheerFZ
@NemanjaTrifunovicRTRK
@NEOatNHNG
@lurtz
@crimson11
@LittleHuba

Agenda

1. Status update SOME/IP
2. Status update Flatbuffers
3. Status update Rust API
4. Status Methods&Fields
5. Status CI/Infrastructure
6. Open bug tickets
7. Short notice topics

Meeting Minutes

to (1)

Meeting to understand what changes are necessary to include SOME/IP in the score_communication repository.
https://github.com/orgs/eclipse-score/discussions/3240#discussioncomment-18330756
Goal:
Use mw::com with GenericProxy/GenericSkeleton as IPC bridge impmlementation
Reduction of state tracking in custom gateway logic

to (2)

Current work focused on score_baselibs. PR is still pending.
@LittleHuba to talk with @4og to put more focus on reviewing this PR.

to (3)

Rust edition was downgraded to 2021 based on feedback from toolchain maintainers.
See https://sdvworkinggroup.slack.com/archives/C09JY2V5E79/p1788454394691239

Rustfmt enforcement is now unblocked and will be enabled by tomorrow @LittleHuba

to (4)

eclipse-score/communication#767 (comment)
We know that a fix is possible. We are still nailing down the details how it will look like.
Midterm solution: Use a thread pool in message_passing to allow higher concurrency. User can size thread pool via configuration.
We unfortunately cannot give a timeline for this yet.

QNX SDP currently has issues with service discovery via inotify that blocks one integration test regarding methods.
We currently wait for adoption of QNX SDP 8.0.5 in S-CORE with the hope that this will resolve the problem.

to (5)

QNX SDP downloads sporadically fail in S-CORE. (not yet seen in communication as a significant problem)
Currently only workaround is to restart the workflow.
In case of problems please reach out to @LittleHuba
Locally you can try https://github.com/eclipse-score/time/blob/main/.bazelrc#L28

rustfmt enforcement pending
Afterwards all core languages of the repository are covered by formatters and static analysis.
Work pending on some ruleset tailoring. C++ Compiler warnings and CodeQL have already been tailored.

Other tooling should enforce rulesets similar to https://github.com/eclipse-score/communication/blob/main/quality/static_analysis/misra_gep.md
There is work from @nradakovic to share the compiler warning sets in score_cpp_policies via cc_features.
There is some work for rust as well: eclipse-score/score_rust_policies#11

to (6)

@LittleHuba to check status eclipse-score/communication#722
@crimson11 @LittleHuba to come up with a short-term solution to at least limit cascading effect of this.
Longterm solution will require fix as commented by @crimson11 in the ticket.

to (7)

QNX unreliability in other repos will be fixed. There is no timeline for this currently but we have people working from S-CORE and QNX on both ends.

S-CORE v0.9 will be released today or tomorrow. As part of that release score_communication takes part with v0.4.0.
No additional release notes are included in S-CORE v0.9 from our side. Please refer to the ones from our release.
The fix for the QNX bug surfaced in baselibs is part of the S-CORE release.