Plugin receiving process and reductor

[kamer16]

gi._glib.GError: plugins' receives both processor and reductor inputs which may deadlock`

Is this error message really necessary ?
My reductor is actually ufo-buffer-task which I am deliberately using to avoid deadlock.

When using a intermediary copy task this error message is silenced. Shouldn't the
error message persist as ultimately the graph is still the same hence the deadlock would
still be present if there was one.

[matze]

That's true. On the other hand, it might really become a problem. So, in order to avoid crapping it out, I could make it a warning or debug message if you agree.

[kamer16]

I don't know what is best. If in the general case it almost always results in a dead lock than maybe the error is okay, so that if the user is REALLY sure he wants such a configuration he uses a copy task to suppress the error. How ever, if it really is that dangerous UFO should look at all the predecessors for dead lock and not just the parent node.