Thank you Michael,
I’ll definitely be looking into this in the future…
--Udo
From: Michael Oleske
Date: Thursday, May 6, 2021 at 9:22 AM
To: dev@geode.apache.org
Subject: Rescued Geode Protobuf
Hi Geode Friends!
Since I didn't see any movement on rescuing Geode Protobuf into another
Hi Geode Friends!
Since I didn't see any movement on rescuing Geode Protobuf into another
repository, I went ahead and did that. It seemed like a better idea to me than
trying to search commit history or old branches with git. It is located at
https://github.com/moleske/geode-protobuf
I'm
This is a review draft of our report to the Apache Board on the Geode
project. Please send me your feedback by Monday, May 10.
In particular, let me know if I omitted any publications or community
outreach efforts.
Thanks,
Dave
## Description:
The mission of Apache Geode is the creation and
Clang format and clang-tidy are enforcing many Google C++ rules and our
deviations from that.
None of those tools enforce naming conventions.
I am not so much looking for this to be a holy war, nor do I think it has even
remotely degraded to that. The original post was to agree on the set of
What are we missing/unable to format with our clang-tools?
These style discussions tend to become holy wars, hopefully we can avoid this...
if we can tool are largest concerns and perform good PR reviews looking for
valid algorithms, good mnemonics naming variables and such I think we'll be
Sorry, our next meeting won't be April 2nd, but June 2nd. Apparently, I've lost
all sense of time during the pandemic.
From: Alexander Murmann
Sent: Wednesday, May 5, 2021 09:39
To: geode
Subject: Today's Community Meeting
Hi everyone!
It was great to see so
Hi everyone!
It was great to see so many folks attend our first community meeting today and
contribute to the discussion. An especially big thank you goes to Alberto Gomez
for presenting his
Hi Anthony-
Thank you for the quick reply.
The Spring Data Team is currently looking ahead towards Java 16 when building
and running Spring Data examples to get a sense for what works and what
doesn't, now that Java 16 is GA along with anticipation for users with
questions or problems.
Thanks for reporting this John. The next LTS version of Java (17) is due later
this year. I think Geode needs to at least support every LTS version of Java
and clearly we would need to fix errors like this. Do you see a need to support
Java 16 now?
Anthony
On May 5, 2021, at 7:57 AM, John
What is the plan to support Java 16 for Apache Geode? Timeframe?
Running Apache Geode on a Java 16 Runtime produces errors like the following:
- org.apache.geode.InternalGemFireException: unable to retrieve underlying byte
buffer
- at
Please, disregard my last e-mail.
I was having a parallel conversation by e-mail with Mario on this topic and
sent the e-mail to the list by mistake.
BR,
Alberto
From: Alberto Gomez
Sent: Wednesday, May 5, 2021 11:29 AM
To: dev@geode.apache.org
Subject: Re:
I think that this is enough.
Šalje: Alberto Gomez
Poslano: 5. svibnja 2021. 11:29
Prima: dev@geode.apache.org
Predmet: Re: Odg: Geode retry/acknowledge improvement
You could answer to their latest e-mail to confirm that Darrel's suspicion
could happen. Let's
You could answer to their latest e-mail to confirm that Darrel's suspicion
could happen. Let's see if in that case they are willing to collaborate.
Alberto
From: Mario Ivanac
Sent: Wednesday, May 5, 2021 11:28 AM
To: dev@geode.apache.org
Subject: Odg: Odg:
Hi,
I think that we have problem that Darrel was suspicious, and that some kind of
notification could be send from peer-to-peer to acknowledge that message is
received on receiving side.
Regarding test with ip tables, execution gets stuck with conserve-sockets set
to false or true.
BR,
Mario
Hi,
I forgot to mention that I enabled ON_DISCONNECT_CLEAR_PDXTYPEIDS property.
Also, I tried a different scenario which does not exactly involves local
PdxType retention, which is:
1. Start a cluster with 1 locator and 3 servers, and persistence is disabled
for PdxTypes.
2. Setup a
15 matches
Mail list logo
