dear:
Dynamically Create Region Demo ，When Geode Server Reboot ,Lost Region
instance
https://geode.apache.org/docs/guide/112/developing/region_options/dynamic_region_creation.html
I don't know why? Hope to help me, thanks!
18911098...@163.com
Done!
> On May 21, 2020, at 9:50 AM, Dave Barnes wrote:
>
> Please add this change to support/1.13, Owen.
> Thanks,
> Dave
>
> On 2020/05/21 16:19:49, Dick Cavender wrote:
>> +1
>>
>> On Thu, May 21, 2020 at 8:57 AM Ju@N wrote:
>>
>>> +1
>>>
>>> On Thu, 21 May 2020 at 16:53, Anthony
Please add this change to support/1.13, Owen.
Thanks,
Dave
On 2020/05/21 16:19:49, Dick Cavender wrote:
> +1
>
> On Thu, May 21, 2020 at 8:57 AM Ju@N wrote:
>
> > +1
> >
> > On Thu, 21 May 2020 at 16:53, Anthony Baker wrote:
> >
> > > +1
> > >
> > > > On May 21, 2020, at 8:51 AM, Owen
+1
On May 21, 2020, 8:51 AM -0700, Owen Nichols , wrote:
Some automated scans have flagged Geode Pulse as potentially containing “high"
security vulnerability CVE-2020-5407.
Analysis shows that this saml vulnerability is not applicable to Geode Pulse.
It is low risk to bump the spring-security
Please proceed with the proposed merge, Juan.
Thanks,
Dave
On 2020/05/21 16:15:59, Udo Kohlmeyer wrote:
> +1..
> On May 21, 2020, 8:12 AM -0700, Ju@N , wrote:
> Hello devs,
>
> I'd like to propose bringing *GEODE-8150 [1] *to the *support/1.13* branch.
> The ticket is basically to revert the
Looks like there's enough consensus already (three +1s), so I've cherry
picked the commit into support/1.13 branch [1].
Best regards.
[1]:
https://github.com/apache/geode/commit/281937d17df639cd416f0e6ce47dd73ed9e8595f
On Thu, 21 May 2020 at 17:16, Udo Kohlmeyer wrote:
> +1..
> On May 21,
+1
On Thu, May 21, 2020 at 8:57 AM Ju@N wrote:
> +1
>
> On Thu, 21 May 2020 at 16:53, Anthony Baker wrote:
>
> > +1
> >
> > > On May 21, 2020, at 8:51 AM, Owen Nichols wrote:
> > >
> > > Some automated scans have flagged Geode Pulse as potentially containing
> > “high" security vulnerability
+1..
On May 21, 2020, 8:12 AM -0700, Ju@N , wrote:
Hello devs,
I'd like to propose bringing *GEODE-8150 [1] *to the *support/1.13* branch.
The ticket is basically to revert the upgrade of the *classgraph* [2]
library, we found some performance issues that are not addressed even when
using the
+1
On Thu, 21 May 2020 at 16:53, Anthony Baker wrote:
> +1
>
> > On May 21, 2020, at 8:51 AM, Owen Nichols wrote:
> >
> > Some automated scans have flagged Geode Pulse as potentially containing
> “high" security vulnerability CVE-2020-5407.
> >
> > Analysis shows that this saml vulnerability
+1
> On May 21, 2020, at 8:51 AM, Owen Nichols wrote:
>
> Some automated scans have flagged Geode Pulse as potentially containing
> “high" security vulnerability CVE-2020-5407.
>
> Analysis shows that this saml vulnerability is not applicable to Geode Pulse.
>
> It is low risk to bump the
+1
While I’d rather see us go all the way back to 4.0.6, this seems like a step in
that direction.
> On May 21, 2020, at 8:30 AM, Anthony Baker wrote:
>
> +1 thanks Juan
>
>> On May 21, 2020, at 8:12 AM, Ju@N wrote:
>>
>> Hello devs,
>>
>> I'd like to propose bringing *GEODE-8150 [1] *to
Some automated scans have flagged Geode Pulse as potentially containing “high"
security vulnerability CVE-2020-5407.
Analysis shows that this saml vulnerability is not applicable to Geode Pulse.
It is low risk to bump the spring-security dependency to the latest version to
avoid false
+1 thanks Juan
> On May 21, 2020, at 8:12 AM, Ju@N wrote:
>
> Hello devs,
>
> I'd like to propose bringing *GEODE-8150 [1] *to the *support/1.13* branch.
> The ticket is basically to revert the upgrade of the *classgraph* [2]
> library, we found some performance issues that are not addressed
Hello devs,
I'd like to propose bringing *GEODE-8150 [1] *to the *support/1.13* branch.
The ticket is basically to revert the upgrade of the *classgraph* [2]
library, we found some performance issues that are not addressed even when
using the latest released version, the full details can be seen
14 matches
Mail list logo
