Github user pivotal-jbarrett commented on the issue:
https://github.com/apache/geode-native/pull/54
This will get closed when pull #63 is committed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user pivotal-jbarrett commented on the issue:
https://github.com/apache/geode-native/pull/54
@dgkimura I will pull this and work on some of the tests.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user pivotal-jbarrett commented on the issue:
https://github.com/apache/geode-native/pull/54
@dgkimura It will give the CI something to chew on to prove that this
message actually works with the server now. ;)
---
If your project is set up for it, you can reply to this email a
Github user dgkimura commented on the issue:
https://github.com/apache/geode-native/pull/54
@pivotal-jbarrett Okay. Fair enough. That's going to add some cycles to
this pull-request.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user pivotal-jbarrett commented on the issue:
https://github.com/apache/geode-native/pull/54
@dgkimura I would suggest getting a few of those integration tests updated
to test this. They were marked flaky a long time ago when the tests ran through
several iterations with differ
Github user dgkimura commented on the issue:
https://github.com/apache/geode-native/pull/54
@echobravopapa We're only human.
Our unittest didn't catch it originally because the output that's written
to DataOutput in the constructor is the same with/without this variable set.
