possible misordering of software actions under certain conditions

[dietrichb]

The main developer claims this is fixed with new (v3) saftlib versions, but I'd like to report this issue here as many people are still using older (v2.5) saftlib versions.

If a client subscribes to software actions with multiple conditions, the actions received for each condition are ordered according to their timestamps. However, actions for different conditions might become received in the wrong order, not sorted according to their timestamps. This seems to be related to a race condition within the (old) saftlib communication and only happens if actions are received with very close deadlines.