Issue: Under high load, non-unique json rpc ids were being generated causing some futures to resolve incorrectly and cause some async tasks behave incorrectly under said high load situations
Fix: Appending UUID to the end of jsonrpc ids ensures uniqueness
Issue: Under high load, non-unique json rpc ids were being generated causing some futures to resolve incorrectly and cause some async tasks behave incorrectly under said high load situations Fix: Appending UUID to the end of jsonrpc ids ensures uniqueness