Hi Kirk,
This has been happening intermittently with the latest Liberica JDK8u282 since
it was released. I worked with the folks at LIberica to reproduce the issue and
they have a fix which will be included in their next release, sometime in April.
Donal
From: K
https://concourse.apachegeode-ci.info/builds/17742 core dumped during
compilation of one of the modules.
I believe exit code 134 means that it failed to fork a new Java VM.
I wonder what would cause a test job to be unable to fork a process. It
seems to have forked processes for compiling all of
We will get these approved as soon as possible.
Regards,
Nabarun
From: Mario Ivanac
Sent: Thursday, March 25, 2021 4:17 AM
To: dev@geode.apache.org
Subject: Odg: [DISCUSS] CODEOWNERS mechanism feedback
Hi all,
just to remind on this topic.
Could we expand list
I worked on the protobuf client/server interface as long as anyone else but
still fail to see the value in keeping it in anything but a branch unless
someone is going to pick it up soon and complete it.
As Dan pointed out, we already have a good interface for storing Json documents
and we never
Hi all,
just to remind on this topic.
Could we expand list of CODEOWNERS in some areas that are bottleneck.
For examples I have 2 PR`s that are waiting on review from WAN area for several
weeks:
https://github.com/apache/geode/pull/6013
https://github.com/apache/geode/pull/6048
BR,
Mario
_
