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

GD-222: Fix error on SignalCollector when emitter is not a Node #228

Merged
merged 1 commit into from
Jul 19, 2023

Conversation

MikeSchulze
Copy link
Owner

Why

When try to use the monitor_signals on a Resource it fails by a Invalid get index 'tree_exiting' (on base: 'Resource (ExampleResource)').

What

  • fixed by test is given emitter from type Node before connect to tree_exiting
  • relase at testsuite end all monitored connected signal

# What
When try to use the `monitor_signals` on a Resource it fails by a `Invalid get index 'tree_exiting' (on base: 'Resource (ExampleResource)').`

# What
- fixed by test is given emitter from type `Node` before connect to `tree_exiting`
- relase at testsuite end all monitored connected signal
@MikeSchulze MikeSchulze self-assigned this Jul 19, 2023
@MikeSchulze MikeSchulze linked an issue Jul 19, 2023 that may be closed by this pull request
@MikeSchulze MikeSchulze merged commit 1224ff6 into master Jul 19, 2023
@MikeSchulze MikeSchulze deleted the GD-222 branch July 19, 2023 17:15
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.

GD-222: monitor_signals does not work with resources
1 participant