[PROPOSAL]: GEODE-8150 into support/1.13
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 in the ticket. The fix has been merged into develop through commit 07bf3dd827f29a5deb8619f79203d94847a1a823 [3]. Best regards. [1]: https://issues.apache.org/jira/browse/GEODE-8150 [2]: https://github.com/classgraph/classgraph [3]: https://github.com/apache/geode/commit/07bf3dd827f29a5deb8619f79203d94847a1a823 -- Ju@N
Re: [PROPOSAL]: GEODE-8150 into support/1.13
+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 even when > using the latest released version, the full details can be seen in the > ticket. > The fix has been merged into develop through commit > 07bf3dd827f29a5deb8619f79203d94847a1a823 [3]. > Best regards. > > [1]: https://issues.apache.org/jira/browse/GEODE-8150 > [2]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclassgraph%2Fclassgraph&data=02%7C01%7Cbakera%40vmware.com%7Cba2b7654573e4e0e88a808d7fd996183%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707519827330&sdata=r0KXJRo2QV%2Bj2ifWk%2B4DhuSHhI0O2AFPKRcP2nNVsfE%3D&reserved=0 > [3]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2F07bf3dd827f29a5deb8619f79203d94847a1a823&data=02%7C01%7Cbakera%40vmware.com%7Cba2b7654573e4e0e88a808d7fd996183%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707519827330&sdata=GLqL%2B%2Fs5Msna8sORi8Bh%2BMJQrPIn2lrnDO8%2F9OKNNy8%3D&reserved=0 > > -- > Ju@N
Proposal to backport GEODE-8167
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 positives in automated scans. This change is already on develop and all tests have passed. It would be nice to include this in 1.13. -Owen
Re: [PROPOSAL]: GEODE-8150 into support/1.13
+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 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 in the >> ticket. >> The fix has been merged into develop through commit >> 07bf3dd827f29a5deb8619f79203d94847a1a823 [3]. >> Best regards. >> >> [1]: https://issues.apache.org/jira/browse/GEODE-8150 >> [2]: >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclassgraph%2Fclassgraph&data=02%7C01%7Cbakera%40vmware.com%7Cba2b7654573e4e0e88a808d7fd996183%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707519827330&sdata=r0KXJRo2QV%2Bj2ifWk%2B4DhuSHhI0O2AFPKRcP2nNVsfE%3D&reserved=0 >> [3]: >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2F07bf3dd827f29a5deb8619f79203d94847a1a823&data=02%7C01%7Cbakera%40vmware.com%7Cba2b7654573e4e0e88a808d7fd996183%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707519827330&sdata=GLqL%2B%2Fs5Msna8sORi8Bh%2BMJQrPIn2lrnDO8%2F9OKNNy8%3D&reserved=0 >> >> -- >> Ju@N >
Re: Proposal to backport GEODE-8167
+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 spring-security dependency to the latest version > to avoid false positives in automated scans. This change is already on > develop and all tests have passed. It would be nice to include this in 1.13. > > -Owen
Re: Proposal to backport GEODE-8167
+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 is not applicable to Geode > Pulse. > > > > It is low risk to bump the spring-security dependency to the latest > version to avoid false positives in automated scans. This change is > already on develop and all tests have passed. It would be nice to include > this in 1.13. > > > > -Owen > > -- Ju@N
Re: [PROPOSAL]: GEODE-8150 into support/1.13
+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 latest released version, the full details can be seen in the ticket. The fix has been merged into develop through commit 07bf3dd827f29a5deb8619f79203d94847a1a823 [3]. Best regards. [1]: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8150&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567034068&sdata=lQ8z8eamQCEzKNwJal0W0k%2B5vjJWguzL8M7vrPPfQhQ%3D&reserved=0 [2]: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclassgraph%2Fclassgraph&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567044068&sdata=vZzkQPvUe7vw2iMxt79rd4cTh6dAjesbrqy8urNVOlA%3D&reserved=0 [3]: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2F07bf3dd827f29a5deb8619f79203d94847a1a823&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567044068&sdata=iuR%2FW3bNjI7LvDlbvo1vxLyoGwp8IS4GyDYsWb%2FuabM%3D&reserved=0 -- Ju@N
Re: Proposal to backport GEODE-8167
+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 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 positives in automated scans. This change is > > already on develop and all tests have passed. It would be nice to > include > > this in 1.13. > > > > > > -Owen > > > > > > -- > Ju@N >
Re: [PROPOSAL]: GEODE-8150 into support/1.13
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, 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 latest released version, the full details can be seen in the > ticket. > The fix has been merged into develop through commit > 07bf3dd827f29a5deb8619f79203d94847a1a823 [3]. > Best regards. > > [1]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8150&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567034068&sdata=lQ8z8eamQCEzKNwJal0W0k%2B5vjJWguzL8M7vrPPfQhQ%3D&reserved=0 > [2]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclassgraph%2Fclassgraph&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567044068&sdata=vZzkQPvUe7vw2iMxt79rd4cTh6dAjesbrqy8urNVOlA%3D&reserved=0 > [3]: > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2F07bf3dd827f29a5deb8619f79203d94847a1a823&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567044068&sdata=iuR%2FW3bNjI7LvDlbvo1vxLyoGwp8IS4GyDYsWb%2FuabM%3D&reserved=0 > > -- > Ju@N > -- Ju@N
Re: [PROPOSAL]: GEODE-8150 into support/1.13
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 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 in the > ticket. > The fix has been merged into develop through commit > 07bf3dd827f29a5deb8619f79203d94847a1a823 [3]. > Best regards. > > [1]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8150&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567034068&sdata=lQ8z8eamQCEzKNwJal0W0k%2B5vjJWguzL8M7vrPPfQhQ%3D&reserved=0 > [2]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclassgraph%2Fclassgraph&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567044068&sdata=vZzkQPvUe7vw2iMxt79rd4cTh6dAjesbrqy8urNVOlA%3D&reserved=0 > [3]: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fcommit%2F07bf3dd827f29a5deb8619f79203d94847a1a823&data=02%7C01%7Cudo%40vmware.com%7C2dac2ec3d111496df0f008d7fd9964d3%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637256707567044068&sdata=iuR%2FW3bNjI7LvDlbvo1vxLyoGwp8IS4GyDYsWb%2FuabM%3D&reserved=0 > > -- > Ju@N >
Re: Proposal to backport GEODE-8167
+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 dependency to the latest version to avoid false positives in automated scans. This change is already on develop and all tests have passed. It would be nice to include this in 1.13. -Owen
Re: Proposal to backport GEODE-8167
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 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 dependency to the latest > > > version to avoid false positives in automated scans. This change is > > > already on develop and all tests have passed. It would be nice to > > include > > > this in 1.13. > > > > > > > > -Owen > > > > > > > > > > -- > > Ju@N > > >
Re: Proposal to backport GEODE-8167
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 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 is not applicable to Geode Pulse. > > It is low risk to bump the spring-security dependency to the latest version to avoid false positives in automated scans. This change is already on develop and all tests have passed. It would be nice to >>> include this in 1.13. > > -Owen >>> >>> -- >>> Ju@N >>> >>
Creating Regions Dynamically
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
