-1 on changing the check
I'm with Owen - let's leave things alone for now.
On 3/17/20, 7:43 PM, "Owen Nichols" wrote:
At least one person on the thread (@anthony) raised concerns but has not
replied since.
Also since this thread was started, the bug that miscounted files has
Hi all,
As Bruce suggested me, I have created a wiki page describing the problem we are
trying to solve:
https://cwiki.apache.org/confluence/display/GEODE/Allow+same+host+and+port+for+all+gateway+receivers
Please let me know if further clarifications are needed.
Also, I have closed the PR I ha
Tips on using AsyncInvocation:
* Always use await() or get()
* Both check and throw any remote exceptions
* Both use GeodeAwaitility Timeout and will throw TimeoutException if it’s
exceeded
* Use await() for Void types and get() when expecting a non-null value
Recent improvements:
Timeout now ge
Hello Dev list,
I'd like to include a fix for GEODE-7763 in release 1.12.0.
The change removes the call to exportValue, preventing a serialization,
when no clients are waiting for the specific event.
The reason why I think it should be in the release is that we noticed a
negative effect on perform
+1
On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh wrote:
> Hello Dev list,
>
> I'd like to include a fix for GEODE-7763 in release 1.12.0.
> The change removes the call to exportValue, preventing a serialization,
> when no clients are waiting for the specific event.
> The reason why I think it sho
+1
On Wed, Mar 18, 2020 at 11:43 AM Nabarun Nag wrote:
> +1
>
> On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh wrote:
>
> > Hello Dev list,
> >
> > I'd like to include a fix for GEODE-7763 in release 1.12.0.
> > The change removes the call to exportValue, preventing a serialization,
> > when no c
+1
On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh wrote:
> Hello Dev list,
>
> I'd like to include a fix for GEODE-7763 in release 1.12.0.
> The change removes the call to exportValue, preventing a serialization,
> when no clients are waiting for the specific event.
> The reason why I think it sho
+1
On 3/18/20, 11:50 AM, "Dan Smith" wrote:
+1
On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh wrote:
> Hello Dev list,
>
> I'd like to include a fix for GEODE-7763 in release 1.12.0.
> The change removes the call to exportValue, preventing a serialization,
>
+1
> On Mar 18, 2020, at 11:49 AM, Dick Cavender wrote:
>
> +1
>
> On Wed, Mar 18, 2020 at 11:43 AM Nabarun Nag wrote:
>
>> +1
>>
>> On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh wrote:
>>
>>> Hello Dev list,
>>>
>>> I'd like to include a fix for GEODE-7763 in release 1.12.0.
>>> The chang
+1
On Wed, Mar 18, 2020 at 11:52 AM Owen Nichols wrote:
> +1
>
> > On Mar 18, 2020, at 11:49 AM, Dick Cavender
> wrote:
> >
> > +1
> >
> > On Wed, Mar 18, 2020 at 11:43 AM Nabarun Nag wrote:
> >
> >> +1
> >>
> >> On Wed, Mar 18, 2020 at 11:41 AM Jason Huynh wrote:
> >>
> >>> Hello Dev list,
>
+1
On Wed, Mar 18, 2020 at 12:32 PM John Blum wrote:
> +1
>
> On Wed, Mar 18, 2020 at 11:52 AM Owen Nichols wrote:
>
> > +1
> >
> > > On Mar 18, 2020, at 11:49 AM, Dick Cavender
> > wrote:
> > >
> > > +1
> > >
> > > On Wed, Mar 18, 2020 at 11:43 AM Nabarun Nag wrote:
> > >
> > >> +1
> > >>
>
+1
On 3/18/20, 11:41 AM, "Jason Huynh" wrote:
Hello Dev list,
I'd like to include a fix for GEODE-7763 in release 1.12.0.
The change removes the call to exportValue, preventing a serialization,
when no clients are waiting for the specific event.
The reason why I think i
There appears to be consensus that this is a critical fix.
The following commit has been brought into release/1.12 as the
critical fix for GEODE-7763:
git cherry-pick -x b4c3e9413f0008635b0a0c9116c96147d1e4ceec
GEODE-7763 has been marked as 'resolved in' 1.12.
Regards
EB
On Wed, Mar 18, 2020
Thanks Kirk. Can you add an example here...
On Wed, Mar 18, 2020 at 11:12 AM Kirk Lund wrote:
> Tips on using AsyncInvocation:
>
> * Always use await() or get()
> * Both check and throw any remote exceptions
> * Both use GeodeAwaitility Timeout and will throw TimeoutException if it’s
> exceeded
One addendum to this proposal:
This proposed method of configuring a SNI proxy server requires that the
client sends the SNI hostname as part of the TLS handshake. In the previous
proposal we suggested it would only be sent if a SNI Proxy is configured.
Now we propose that a geode client will *alw
Hello devs,
I'd like to propose including the fixes for *GEODE-7832 [1]*, *GEODE-7853
[2]* and *GEODE-7863 [3]* in release 1.12.0.
All the changes are related to the work we have been doing in order to
bring the performance closer to the baseline (*Geode 1.10*), we are not
quite there yet but it w
+3
> On Mar 18, 2020, at 4:52 PM, Ju@N wrote:
>
> Hello devs,
>
> I'd like to propose including the fixes for *GEODE-7832 [1]*, *GEODE-7853
> [2]* and *GEODE-7863 [3]* in release 1.12.0.
> All the changes are related to the work we have been doing in order to
> bring the performance closer to t
+1
> On Mar 18, 2020, at 4:13 PM, Dan Smith wrote:
>
> One addendum to this proposal:
>
> This proposed method of configuring a SNI proxy server requires that the
> client sends the SNI hostname as part of the TLS handshake. In the previous
> proposal we suggested it would only be sent if a SNI
+1
On Wed, Mar 18, 2020 at 4:53 PM Owen Nichols wrote:
> +3
>
> > On Mar 18, 2020, at 4:52 PM, Ju@N wrote:
> >
> > Hello devs,
> >
> > I'd like to propose including the fixes for *GEODE-7832 [1]*, *GEODE-7853
> > [2]* and *GEODE-7863 [3]* in release 1.12.0.
> > All the changes are related to th
19 matches
Mail list logo
