feat(deps): add score_config_management to reference integration by Chahult · Pull Request #299 · eclipse-score/reference_integration

Chahult · 2026-07-27T07:40:34Z

Added score_config_management module (commit ) to known_good.json under target_sw with code_root_path //score/config_management/...
Regenerate bazel_common/score_modules_target_sw.MODULE.bazel

Chahult · 2026-07-29T04:44:09Z

Hi @pawelrutkaq @PiotrKorkus @nradakovic @antonkri @AlexanderLanin , could someone please unlock this workflow and review our changes? Thanks!

Chahult · 2026-07-29T09:20:45Z

Updated the baselibs to the latest version as builds are breaking.

LittleHuba · 2026-07-29T09:36:43Z

Updated the baselibs to the latest version as builds are breaking.

Please bump to the version pulled in by communication. That gives you a good chance to have a successful build.

Pin score_config_management to 49f26b74 and add a patch (sourced from config_management PR#37) fixing the ProxyFuture API migration and removing SOCAL/component_tests targets not present in the OSS build.

github-actions · 2026-08-10T09:52:44Z

The created documentation from the pull request is available at: docu-html

Chahult · 2026-08-10T10:05:24Z

Hi @pawelrutkaq @PiotrKorkus , could you please review and approve these changes? The aim of this PR is to add score_config_management to the reference integration.

pawelrutkaq

Two points

please deploy the example (from your repo) in showcases as other modules does
please at least setup correctly module in bazel registry (no need of release ) -> already done

pawelrutkaq · 2026-08-11T05:50:00Z

+                "repo": "https://github.com/eclipse-score/config_management.git",
+                "hash": "b22ca9bd222b99985be4339187c639d6862051a0",
+                "bazel_patches": [
+                    "patches/config_management/001-fix-communication-api-and-remove-targets.patch"


Since this looks like an arbitrary patch, someone from com shall ack it.

The current name 001-fix-communication-api-and-remove-targets.patch is misleading — the patch doesn't fix the communication library, it adapts config_management to the new ProxyFuture API and removes internal/ARA-specific targets. Let me rename it

Please do not integrate new module with patches, please fix it upstream

The OptionalProxyData → ProxyFuture part of the patch is a temporary mismatch caused by an in-progress mw::com migration: the internal main repo still uses the old OptionalProxyData API, while the OSS communication repo has already migrated to ProxyFuture. Once that migration completes and syncs upstream, config_management's main repo will use ProxyFuture too, and this part of the patch will no longer be needed — no upstream fix is possible for this piece yet.

pawelrutkaq · 2026-08-11T05:50:14Z

+                        "//score/config_management/config_daemon/code/services/details/mw_com:unit_test",
+                        "//score/config_management/config_provider/code/config_provider/factory:unit_tests_mw_com",
+                        "//score/config_management/config_provider/code/proxies/details:unit_test_mw",
+                        "//score/config_management/dependability/..."


why we need those exclusions ?

1.mw_com tests: require a running LoLa/SOME/IP runtime — the tests themselves are tagged "exclusive" because "Sandboxing is not properly working with LoLa message passing 2.0". Same reason score_communication excludes //score/mw/com/impl:unit_test_runtime_single_exec and //score/mw/com/impl:runtime_test.

2.dependability/...: these are component/dependable_element safety-metadata targets from score_tooling, not executable tests. Including //... without filtering them would cause build failures.

pawelrutkaq

If comm has already this change in, I would suggest to update com as well here.

pawelrutkaq · 2026-08-14T06:21:19Z

I see that there are some errros in CFM example (especially from CFG daemon):

63ns Starting example 'Config Management Daemon Example'
6.54µs App 1: starting /showcases/bin/config_daemon
App 1: spawned command cd "/showcases/data/config_management" && "/showcases/bin/config_daemon" "-s" "/showcases/data/config_management/etc/mw_com_config.json"
mw::log initialization error: Error No logging configuration files could be found. occurred with context information: Failed to load configuration files. Fallback to console logging.
2026/08/13 06:22:57.2177293 4153009148 000 ECU1 NONE lola log warn verbose 1 <maxSamples> property for event is DEPRECATED! use <numberOfSampleSlots> property for event
2026/08/13 06:22:57.2177293 4153009156 000 ECU1 NONE LM log error verbose 3 [Lifecycle client] FD  111  is invalid for kRunning report
2026/08/13 06:22:57.2177293 4153009156 000 ECU1 NONE App log error verbose 3 ConfigDaemon:: Run Failed to create InitialQualifierStateSender callback
2026/08/13 06:22:57.2177293 4153009156 000 ECU1 NONE DFLT log error verbose 1 Error occurred during Run

NicolasFussberger · 2026-08-14T08:48:41Z

I see that there are some errros in CFM example (especially from CFG daemon):

63ns Starting example 'Config Management Daemon Example'
6.54µs App 1: starting /showcases/bin/config_daemon
App 1: spawned command cd "/showcases/data/config_management" && "/showcases/bin/config_daemon" "-s" "/showcases/data/config_management/etc/mw_com_config.json"
mw::log initialization error: Error No logging configuration files could be found. occurred with context information: Failed to load configuration files. Fallback to console logging.
2026/08/13 06:22:57.2177293 4153009148 000 ECU1 NONE lola log warn verbose 1 <maxSamples> property for event is DEPRECATED! use <numberOfSampleSlots> property for event
2026/08/13 06:22:57.2177293 4153009156 000 ECU1 NONE LM log error verbose 3 [Lifecycle client] FD  111  is invalid for kRunning report
2026/08/13 06:22:57.2177293 4153009156 000 ECU1 NONE App log error verbose 3 ConfigDaemon:: Run Failed to create InitialQualifierStateSender callback
2026/08/13 06:22:57.2177293 4153009156 000 ECU1 NONE DFLT log error verbose 1 Error occurred during Run

I assume the error regarding lifecycle is that the config manager uses the lifecycle API to report running state, but it is not started by Launch Manager so the IPC channel is not actually available.
I think this has no other consequences for the demo despite the error log.

Chahult · 2026-08-14T12:17:23Z

Error happens in config_management:
score::mw::service (the generic service-registration framework in communication) has no real implementation yet — only a stub, added without verifying it actually works with ConfigDaemon.
Even with that fixed, the "demo" only proves ConfigDaemon can call OfferService() successfully and stay alive — it's an in-process stub, not the real LoLa/mw::com IPC backend (that migration is still ongoing in SPP).
Root conclusion: with only a stub mw::service, we can show the daemon starts and doesn't crash, but we cannot demonstrate any real service behavior, because there's no client and no real backend to show data flowing.

Proposed path forward:
Preferred: merge score_config_management into the reference_integration PR without a demo example — avoids implying functionality that doesn't exist yet.
If a demo is mandatory: provide a stub demo with no real service implementation — i.e., just start ConfigDaemon, confirm it comes up and stays alive without crashing, purely to unblock the PR from pending state. This would not demonstrate the service actually being consumed.
We can revisit a real, meaningful demo once mw::service has a proper implementation and the SPP mw::com migration lands.

pawelrutkaq · 2026-08-17T12:24:03Z

Please make PR green, in the example description, write non functional yet and we are good. Keep in mind that the patch You add shall be removed until 0.9, which is 07.09.2026

Chahult · 2026-08-17T12:45:20Z

Please make PR green, in the example description, write non functional yet and we are good. Keep in mind that the patch You add shall be removed until 0.9, which is 07.09.2026

Sure, currently we are working on that part where we will remove this patch and add a proper demo example.

Resolves the conflicts GitHub reported on PR280 via the correct main -> PR1 -> PR2 chain rather than merging main directly. - known_good.json: main's version pins with PR2's audited Stage-2 test-selection schema (bazel_config / exclude_test_targets / exclude_test_target_reasons). - MODULE.bazel.lock, bazel_common/score_modules_target_sw.MODULE.bazel and rust_coverage/BUILD are generated; regenerated rather than hand-merged. - internal_tests.yml keeps //scripts:all_python_unit_tests, a superset of the two targets PR1 named. - Restores generate_override_directive()'s repo_commit_dict parameter: PR1 dropped it while PR2 refactored its caller to pass it, so the auto-merge would have shipped a TypeError breaking --repo-override. - Fixes update_module_from_known_good.py --output-dir-coverage, which crashed on str / str despite being the invocation its own docstring documents. score_config_management keeps main's exclusion list verbatim; it only gains the exclude_test_target_reasons entries PR2's loader requires, worded from eclipse-score#299 and the patch it references. The module still cannot run in Stage 2 (its OSS sources reference an internal-only package that only ref_int's patch removes, and Stage 2 does not patch the module under test) - left for a follow-up. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Chahult requested review from AlexanderLanin, FScholPer, MaximilianSoerenPollak, PiotrKorkus, antonkri, dcalavrezo-qorix, lurtz, nradakovic, opajonk and pawelrutkaq as code owners July 27, 2026 07:40

Chahult force-pushed the feat/add_score_config_management branch from bd6eea0 to 78bd1c3 Compare July 29, 2026 04:30

LittleHuba previously approved these changes Jul 29, 2026

View reviewed changes

Chahult dismissed LittleHuba’s stale review via bd8ae34 July 29, 2026 09:18

Chahult force-pushed the feat/add_score_config_management branch from 78bd1c3 to bd8ae34 Compare July 29, 2026 09:18

Chahult requested a review from LittleHuba July 29, 2026 09:19

Chahult force-pushed the feat/add_score_config_management branch 12 times, most recently from de696a5 to 3e1e4d9 Compare July 31, 2026 10:11

feat(deps): add score_config_management to reference integration

a9899c5

Pin score_config_management to 49f26b74 and add a patch (sourced from config_management PR#37) fixing the ProxyFuture API migration and removing SOCAL/component_tests targets not present in the OSS build.

Chahult force-pushed the feat/add_score_config_management branch from c017095 to a9899c5 Compare August 10, 2026 09:21

ci: re-trigger CI

6d75cbd

michaelsaborov previously approved these changes Aug 10, 2026

View reviewed changes

pawelrutkaq requested changes Aug 11, 2026

View reviewed changes

ci: re-trigger CI

ddbf651

Chahult dismissed michaelsaborov’s stale review via ddbf651 August 11, 2026 06:35

Chahult force-pushed the feat/add_score_config_management branch 5 times, most recently from d717f5d to cf3520b Compare August 12, 2026 06:42

Chahult requested a review from pawelrutkaq August 12, 2026 06:57

Chahult force-pushed the feat/add_score_config_management branch from cf3520b to 30c1273 Compare August 17, 2026 06:40

feat: add config_management showcase

9d5e659

Chahult force-pushed the feat/add_score_config_management branch from 30c1273 to 9d5e659 Compare August 17, 2026 12:41

docs: mark config_management showcase as non functional yet

80d56cd

Chahult force-pushed the feat/add_score_config_management branch from 2b26fb0 to 80d56cd Compare August 17, 2026 12:50

ci: re-trigger CI

e231c15

pawelrutkaq approved these changes Aug 17, 2026

View reviewed changes

pawelrutkaq merged commit 9143efa into eclipse-score:main Aug 17, 2026
16 checks passed

Uh oh!

Conversation

Chahult commented Jul 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Chahult commented Jul 29, 2026

Uh oh!

Chahult commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LittleHuba commented Jul 29, 2026

Uh oh!

github-actions Bot commented Aug 10, 2026

Uh oh!

Chahult commented Aug 10, 2026

Uh oh!

pawelrutkaq left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pawelrutkaq Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

Chahult Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

pawelrutkaq Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

Chahult Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

pawelrutkaq Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

Chahult Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

pawelrutkaq left a comment

Choose a reason for hiding this comment

Uh oh!

pawelrutkaq commented Aug 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NicolasFussberger commented Aug 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Chahult commented Aug 14, 2026

Uh oh!

pawelrutkaq commented Aug 17, 2026

Uh oh!

Chahult commented Aug 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Chahult commented Jul 27, 2026 •

edited

Loading

Chahult commented Jul 29, 2026 •

edited

Loading

pawelrutkaq left a comment •

edited

Loading

pawelrutkaq commented Aug 14, 2026 •

edited

Loading

NicolasFussberger commented Aug 14, 2026 •

edited

Loading