Should push promotion messages from nonatomicactiveevents to their children atomicactiveevents.  See issue #8 in github.
Emitting rpcs with no arguments used to cause a syntax error in java because Arrays.asList() with no arg is incorrect.  Fixed by checking number of rpc args before emitting Arrays.asList().
For backout messages sent over the network, forgot to set their uuids.  Led to throwing an error that did not know how to decode message on receiving endpoint.
Got rid of irritating warnings about pushing updates for Lamport clocks to connected endpoints.  Created an issue for it instead (#27 in github).
Encountering a bug where receiving a message that is a reply to an unknown message request.  In trying to track it down, realized it would help to narrow interface of what can and cannot write to to_reply_with_uuid.
Had an issue where might be sending back an invalid reply uuid.
Previously, in an AtomicActiveEvent,

If we make a partner call and receive a response, we update our
ExecutingEventContext's reply_with_uuid field.  If we then issue
another partner rpc or retry our atomic event, causing the same rpc to
issue, then we used the old reply_with_uuid field.

To solve, any time sending a partner message (instead of a response to
a partner message), just set null as reply_to_uuid field of message.
Added a test to try to ensure that promotion is working properly across partners.  (It's not.)  Test currently uncovered a bug that was filed as issue #28 in github (we're re-generating events that have been backed out).