Skip to content

LmControl API - Support callback registration before connection - #849

Open
NicolasFussberger wants to merge 1 commit into
eclipse-score:mainfrom
etas-contrib:fix_lmcontrol_concurrent_issue
Open

NicolasFussberger wants to merge 1 commit into
eclipse-score:mainfrom
etas-contrib:fix_lmcontrol_concurrent_issue

Conversation

@NicolasFussberger

Copy link
Copy Markdown
Contributor

Fixes a bug where previously LmControl API would crash if the activation callback is registered before a connection had been established to the Launch Manager.

Problematic sequence:
User: register_run_target_activation_callback()
-> onActivationResult()
-> readActivationEvents() <-- Assumes that proxy is already created

Now onActivationResult() is only called if the proxy object has already been created (i.e. connection already established).

@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-849: https://eclipse-score.github.io/lifecycle/pr-849/

This branch is waiting to be deployed

1 waiting deployment
workflow-approval — cb55c914 Waiting Oct 23, 2026 by NicolasFussberger via Build and test unit-tests-arm64-qnx / approval #1734
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant