Processor service: Event processing issues fix attempt 3 #134
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.
Changelog Description
Another attempt to fix issues with processor service that pretends to process events, but not doing anything.
Additional info
If event hub finds out it is diconnected, it does not try to get more events and stops the loop.
Added option to discover event handler classes without having
register
method in the file -> this might help to avoid garbage collection of handler objects ??? possible cause1
on range0-10
???.More context
Processor still prints
"Processing event"
message, so it does fetch AYON events, but either ftrack connection does not exist, or subscribers are not available anymore.Testing notes: