Created test cases that show inconsistent error handling with OnNextValue and toString
Fixed OnNextValue to not call toString on the failing value
Added a renderValue function to create a string from unknown client objects without calling toString (PR #1401)
Merge pull request #1401 from samhendley/onnextvalue

OnError while emitting onNext value: object.toString