Fix registered targets lost when re-launching on existed server #355
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.
This was reported in Gitter 👉 February 3, 2020 4:54 PM from @BigRoy .
It was a bug after #347, it was trying to solve #335 which was assigning and changing targets via
pyblish_qml.api.show
. But the solution did not pay attention to the case that is using targets frompyblish.api.registered_targets
, hence we got the bug.Reproducible
What's changed
targets
is providedtargets
changes toNone
instead of mutablelist