Skip to content

Fix python actor event group callback routing - #316

Merged
tedwaine merged 1 commit into
AcademySoftwareFoundation:developfrom
tedwaine:develop
Jul 29, 2026
Merged

Fix python actor event group callback routing#316
tedwaine merged 1 commit into
AcademySoftwareFoundation:developfrom
tedwaine:develop

Conversation

@tedwaine

Copy link
Copy Markdown
Collaborator

A small fix to correct a longstanding problem where setting up an event callback to watch event messages on a certain actor in Python does not work correctly.

In py_context.cpp a watcher actor subscribes to the desires event group and receives messages. It uses the address of the event group to register an ID for the python callback method to run when an event message is incoming from the event group. The problem was that the event messages appear to originate from the PARENT of the event_group through which events are broadcast, so when it tries to match up the sender of the message with the event_group actor address to work out which python methods to execute it can't do it.

Now when we set-up the routing we get the parent actor address of the event_group and use this to identify which python callbacks should be executed.

Signed-off-by: Ted Waine <ted.waine@gmail.com>
@tedwaine
tedwaine merged commit 271c87c into AcademySoftwareFoundation:develop Jul 29, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant