Base Libs FT Meeting Minutes 2026

[4og]

All regular meetings of the Base Libs Feature Team will be documented in this thread. If you subscribe here, you'll get summaries of the meetings you missed.

[4og]

Weekly 2026-01-07

Participants

@4og
@LucaFgr
@Erikhu1
@aschemmel-tech
@rtrippel-dfine
@paulquiring
@halnasri
@rahulthakre29
@Priyanka-Patil18
@ssingh2099

Agenda & Meeting Minutes

1. S-CORE 0.5 Beta release. https://eclipse-score.github.io/score/main/score_releases/score_releases/score_v0_5_beta.html
   • todo: bring changes from the release branch to main.
2. vajson change request will be discussed at the Architecture Community meeting next week. https://github.com/orgs/eclipse-score/discussions/472#discussioncomment-15414444
3. Current state of TSF for JSON
   • Should it go to the 0.5 final release?
     • Add nlohmann_json to bazel registry and update dependency in baselibs module #1993 is a prerequisite
     • reference integration should have nlohmann json as a dependency, and the docs should be added to https://eclipse-score.github.io/reference_integration/main/
     • open question: is it ok to have inc_ repo in the bazel registry? @4og to bring this to the S-CORE FT leads & communities alignment meeting.
4. PRs up for review:
   • Define AoU requirements for filesystem lib #2360

[4og]

Regarding the open point: I updated #1993 based on the outcome of the alignment meeting. The inc_ can be removed from the name.

[4og]

Weekly 2026-01-14

Participants

@4og
@FelixMoelders
@halnasri
@paulquiring
@OliverHeilwagen
@LucaFgr
@Erikhu1
@linnealinnea
@Priyanka-Patil18
@ssingh2099

Agenda & Meeting Minutes

1. S-CORE 0.5 Final release is shifted to end of February. The cadence of future releases is planed to be changed.
   • The changes made in the baselibs release branch for 0.5 beta release have been moved to main.
2. Change request to introduce vajson library:
   • Discussed in the Architecture Community meeting: https://github.com/orgs/eclipse-score/discussions/472#discussioncomment-15414444
   • Next steps:
     • Finalize docs: Adding requirements and a component change request for vajson #2358 - @linnealinnea
     • Dump the code to https://github.com/eclipse-score/inc_json - this will be started in about two weeks.
     • Make the code compliable
     • Dump safety documentation
     • Convert documentation to the S-CORE format -> Support from the community will be needed.
3. TSF for nlohmann_json
   • Add nlohmann_json to bazel registry and update dependency in baselibs module #1993 - Unblocked and can be worked on.
   • Persistent data storage like test reports - Suggestion is to store files in repository releases.
   • Code scanning alerts - some of them are already resolved, and some need to be dismissed. @4og can dismiss alerts.
4. Documentation migration for baselibs - on pause until process: add DR-005 for independent feature delivery #2346 is complete.
5. Handling of dynamic memory in S-CORE - currently there are not guidelines in S-CORE for it. It would be nice to add one.

[4og]

Weekly 2026-01-21

Participants

@4og
@FelixMoelders
@LucaFue
@halnasri
@OliverHeilwagen
@rahulthakre29
@Priyanka-Patil18
@arsibo
@ssingh2099
Thomas Clausnitzer
@paulquiring
@aschemmel-tech

Agenda & Meeting Minutes

1. New release strategy for S-CORE: https://github.com/orgs/eclipse-score/discussions/2383#discussion-9297512
2. Migrate to score_bazel_cpp_toolchains baselibs#70 - waiting for the https://github.com/eclipse-score/bazel_cpp_toolchains release. Strict warnings currently cannot be enabled due to many compilation errors.
3. Update on TSF
   • Internal review for Bug: Unresolved review comments in TA-ANALYSIS nlohmann_json#10, PR will be created soon. @aschemmel-tech will review it.
   • There will be proposal for dealing with C++ exceptions in nlohmann_json. To be presented next week.
   • Rename inc_nlohmann_json repo to nlohmann_json .eclipsefdn#127
4. ABI compatible data types
   • Current status is unknown. To be discussed next week.

[4og]

Weekly 2026-01-28

Participants

@4og
@aschemmel-tech
@halnasri
@linnealinnea
@FelixMoelders
Thomas Clausnitzer
@ShoroukRamzy
@rahulthakre29
Ingo Matheis
@NEOatNHNG
@rtrippel-dfine
@atarekra
@sankurm
@Rutik7

Agenda & Meeting Minutes

1. New workflows in baselibs repo
   • https://github.com/eclipse-score/baselibs/tree/main/.github/workflows
   • Known issues:
     • Bazel cache is not working well. Attempt to fix it: Improve Bazel cache behavior: restrict writes to pushes and add optional disk-cache input for QNX workflow cicd-workflows#56
     • Missing copyrights in a few files and duplicated copyrights. Bug: multipe copyrights baselibs#82
2. Proposal for dealing with C++ exceptions in nlohmann_json
   • it's possible to disable exceptions using a runtime parameter allow_exceptions. It's available in parse API.
   • The lib would still throw on API misuse cases. Thomas Clausnitzer will provide a link for that.
   • Thomas Clausnitzer will check if error message is captured on parse error.
   • Check if any changes in https://github.com/eclipse-score/baselibs/tree/main/score/json/internal/parser/nlohmann are needed.
3. Update on TSF
   • Meeting with Exida is planned on Friday.
   • Resolve TA-ANALYSIS Feedback and Adapt nlohmann pipeline to check s-core matrix specification nlohmann_json#16 - Special handling is needed. See "!! important information !!" section.
4. ABI compatible data types
   • https://eclipse-score.github.io/score/main/features/communication/abi_compatible_data_types/index.html
   • @4og and @pawelrutkaq will work on creating a roadmap for this component.
   • Some rust types have already been implemented in [Rust] Base containers baselibs_rust#6
   • There is some activity in communication FT regarding implementing a variant type. @sankurm will arrange github issues.
   • @NEOatNHNG also needs a variant/union type to exchange data between two C++ processes via mw::com.
   • IDL topic still needs alignment in Architecture community. This will be required at some point for the SOME/IP serialization/deserialization. It's also needed for Rust-C++ interoperability.

[TClausnitzer]

Hi, quick follow-up with the nlohmann/json exception reference, this is the link to the official docu.

As to more details on possible throws with API misuse:

• In the baselibs wrapper the nlohmann usage is limited to nlohmann::json::parse(...) with a parser callback (parse_event_t) and basic type checks/conversions in the callback path. For the most common error, malformed JSON text, the only relevant nlohmann parse error class is json.exception.parse_error.101. As we talked about in the call, this is the error that does not throw with the parameter parse(..., allow_exceptions=false).

• I suspected some possible other throws for API misuse, such as parse error 104 - 115 or error 2xx- 5xx. On a closer look, none of these errors can occur in the current wrapper code path, but only during use of other nlohmann functions such as at(), patch(), etc.

• Any remaining "throw/abort" scenarios would be general C++ runtime failures (e.g. OOM) or would require changes of the wrapper to use additional nlohmann APIs.

[4og]

Weekly 2026-02-04

Participants

@4og
@aschemmel-tech
@rtrippel-dfine
@TClausnitzer
@OliverHeilwagen
@FelixMoelders
VPeddina
@atarekra

Agenda & Meeting Minutes

1. S-CORE release milestones:
   • https://github.com/eclipse-score/score/milestones
2. Baselibs repo
   • New release: https://github.com/eclipse-score/baselibs/releases/tag/v0.2.3
   • Issue with new gcc toolchain: Analyze and resolve issues caused by strict_warnings toolchain feature from score_bazel_cpp_toolchains baselibs#97
   • Limited support for AArch64 Linux: Baselibs doesn't work on AArch64 Linux due to libacl dependency being x86_64 only baselibs#78
3. Update on TSF and nlohmann
   • Add nlohmann_json to bazel registry and update dependency in baselibs module #1993 - in progress
   • Update on certification based on feedback from the assessors - We're on a good path! Once certification process started, it's expected to take ~3 months. Possibly, it will be funded by the Eclipse Foundation as it's a strategic topic that demonstrates usage of TSF. Certification process is expected to start around November 2026 according to the current plan. Follow-up meeting on the certification topic is planned on 13.02.2026.
   • Error handling
4. ABI compatible data types
   • Epics: ABI compatible data types baselibs#86 and [Rust] Base containers baselibs_rust#6

[TClausnitzer]

As promised in the call, here are the two slides I showed during our call conscerning the exception handling in nlohmann/json. As a short summary, we currently already have exception handling in our glue wrapper, which returns a message indicating a parsing error, but no detailed diagnostic message.

To obtain detailed diagnostics about the parsing errors, we would need to use sax_parse() using a custom SAX interface. As of yet, no final decision has been made on switching to sax_parse(), I will explore further what that would mean in terms of security concerns, performance and dynamic memory.

Exception Handling in nlohmann.pptx