You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/26 19:18:00 UTC
[jira] [Commented] (GEODE-6961) Server error messages may contain
leading whitespace
[ https://issues.apache.org/jira/browse/GEODE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938893#comment-16938893 ]
ASF subversion and git services commented on GEODE-6961:
--------------------------------------------------------
Commit da0a4bb4e72c17fb8ab3d53c56eb5a23beede4a6 in geode-native's branch refs/heads/master from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=da0a4bb ]
GEODE-6961: Trim leading whitespace from server error message (#503)
> Server error messages may contain leading whitespace
> ----------------------------------------------------
>
> Key: GEODE-6961
> URL: https://issues.apache.org/jira/browse/GEODE-6961
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Blake Bender
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While debugging test failures, I discovered that a negative test case for `Region::PutAll` was failing on _only one_ of our test machines, because the Geode server returns an error string on our Linux test machine which contains _no_ leading whitespace, but the same error string on our Mac test box starts with _one_ leading space. The simple fix is to trim the leading space in the native client, but perhaps it's worth a bit of someone's time later on to determine what the difference is actually about.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)