You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@geode.apache.org by "pdxcodemonkey (GitHub)" <gi...@apache.org> on 2018/11/09 22:05:01 UTC

[GitHub] [geode-native] pdxcodemonkey opened pull request #400: GEODE-5957: Parse (previously) unknown server error messages

- All are just essentially string error messages
- Provides more detail about what happened on server

Co-authored-by: Matthew Reddington <mr...@pivotal.io>

[ Full content available at: https://github.com/apache/geode-native/pull/400 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-native] pdxcodemonkey commented on pull request #400: GEODE-5957: Parse (previously) unknown server error messages

Posted by "pdxcodemonkey (GitHub)" <gi...@apache.org>.

Fixed.

[ Full content available at: https://github.com/apache/geode-native/pull/400 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-native] moleske commented on pull request #400: GEODE-5957: Parse (previously) unknown server error messages

Posted by "moleske (GitHub)" <gi...@apache.org>.

Is `EXPECT_THROW` not sufficient?  A `try` statement in a test always makes me a little jumpy

[ Full content available at: https://github.com/apache/geode-native/pull/400 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-native] pdxcodemonkey closed pull request #400: GEODE-5957: Parse (previously) unknown server error messages

Posted by "pdxcodemonkey (GitHub)" <gi...@apache.org>.

[ pull request closed by pdxcodemonkey ]

[ Full content available at: https://github.com/apache/geode-native/pull/400 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org