-1. Happy to change my mind if there’s a user-friendly way to deal with the
scenario I mentioned below.
Anthony
On Jul 14, 2020, at 8:40 AM, Owen Nichols
mailto:onich...@vmware.com>> wrote:
Hi Anthony, there is a separate discuss thread [1] for this topic. This is the
vote thread for the
Thanks for looking into this, Mario!
You are probably right, that the underlying issue might have been
pre-existing and that the test is surfacing it. I am glad though that you
are investigating, because a close to 30% fail rate is a problem. Something
like this happens every once in a while and
Hi Anthony, there is a separate discuss thread [1] for this topic. This is the
vote thread for the ASF INFRA ticket [2] to make this one specific change that
came out of the discussion. Your input is valuable and I encourage you to both
vote on this thread and continue the conversation on the
+1
On Fri, 10 Jul 2020 at 15:52, Alberto Bustamante Reyes
wrote:
> +1
>
> De: Joris Melchior
> Enviado: viernes, 10 de julio de 2020 15:54
> Para: dev@geode.apache.org
> Asunto: Re: [VOTE] change Default branch for geode-examples to 'develop'
>
> +1
>
> On
Consider the use case of an application developer who wants to run
geode-examples against the latest geode release:
1) brew install apache-geode
2) git clone geode-examples
3) Get some runtime errors because geode-examples won’t connect to a previous
geode release
At this point, you have to do
Hi,
after adding additional checks in failing test, now I can see that test are
failing due to fault that some batch are distributed at stopping of GW sender.
Cause of that, I suspect that this problem existed prior to this PR, but this
PR is first to introduce test to check this.
I will
