Hello Yoram,
It may be better to post this kind of inquires to u...@geode.apache.org
rather than dev@geode.apache.org, but could you provide any log messages
with locators vms, for clarifying what was wrong?
Thanks, regards.
--
Akihiro Kitada | Staff Customer Engineer | +81 80 3716 3736
Sup
Following up on this thread - I finally got around to getting these changes
merged in!
A couple of things to note:
- If you use regular Awaitility, your code will now fail spotless. Use
GeodeAwaitility instead. Now there is no need to set any timeouts, poll
delays, etc in your individual tests.
---
Spring Data GemFire > Nightly-ApacheGeode > #1074 was successful.
---
Scheduled
2458 tests in total.
https://build.spring.io/browse/SGF-NAG-1074/
--
Thi
Following up on this - is there anything we still need to do before we cut
the 1.8 release branch in 2 weeks?
Overall I think the native client source code looks like it's in good shape
- we're running rat, the LICENSE and NOTICE look good, no binaries in the
source, etc.
For cutting the release
That a great suggestion. I will see if I can add a new page.
On Thu, Oct 18, 2018 at 11:21 AM Swapnil Bawaskar
wrote:
> Would it make sense to put these under an "extensions" page, rather than a
> "community" page?
>
> On Tue, Oct 16, 2018 at 5:05 PM Sai Boorlagadda >
> wrote:
>
> > Thanks, Joh
Would it make sense to put these under an "extensions" page, rather than a
"community" page?
On Tue, Oct 16, 2018 at 5:05 PM Sai Boorlagadda
wrote:
> Thanks, John for your inputs. I will be adding the page to capture these
> details.
> If there are no objections then I would go ahead and add a n
