Replication incomplete on duplicate key

Problem is still unsolved: MDEV-37205

Since I am unable to reopen issues which are still unresolved, I have to write a new ticket.

To your comment "Use ORDER BY in your updates to have a predictable update order."

This might be a solution in a single case. But please keep in mind, that replication should be transparent to the application.
In case the statement on the primary table causes an error, and some data has been changed, the statement should be replicated with the pimary/unique key which references the changed data sets.

Replication should be relyable and the replicate should always follow the master, even in error cases. The error case should not be the default, so it is absoultely ok to use a more inefficient way for synchronysing the slave.