Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tracing] Remove exceptions when no traced objects #100

Merged
merged 1 commit into from
May 3, 2019

Conversation

ebousse
Copy link
Contributor

@ebousse ebousse commented Apr 30, 2019

Recently a change was made to throw exceptions when a reference stored in a trace cannot find a traced object as target. However, in such cases, the trace should actually simply store a reference to the original object of the executed model, and not to the traced object (eg. to point to a purely static "current state" in an FSM, while State is not a dynamic class at all and should not be).

This PR remove the exceptions and switches to the expected behavior.

Signed-off-by: Erwan Bousse <erwan.bousse@ls2n.fr>
@dvojtise
Copy link
Contributor

dvojtise commented May 3, 2019

the changes look good to me and the CI is OK

@dvojtise dvojtise merged commit 2ee29e1 into master May 3, 2019
@dvojtise dvojtise added the bug label May 3, 2019
ebousse added a commit that referenced this pull request Jun 7, 2019
Signed-off-by: Erwan Bousse <erwan.bousse@ls2n.fr>
@ebousse ebousse deleted the fix-trace-constructor-refs branch June 7, 2019 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants