[tracing] Remove exceptions when no traced objects #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.