Just checking, is anyone familiar enough with SSL to comment on the proposed
change?
Anthony
> On Oct 29, 2019, at 2:44 AM, Mario Ivanac wrote:
>
> Hi,
>
> We are trying to find a solution for an situation we have. Below is the
> explanation of the issue, as well as a proposed way forward.
Welcome Szu-Yu Lo! Please reach out if you have any questions :-)
Anthony
> On Oct 31, 2019, at 1:30 PM, Szu-Yu Lo wrote:
>
> Thank you so much
>
> On Thu, Oct 31, 2019 at 2:19 PM Dan Smith wrote:
>
>> Hi Szu-Yu Lo,
>>
>> You should have access now. Thanks for being interested in contribu
Hi Dan,
Can you provide me with the ability to assign tickets to myself as well?
Username: joris.melchior
Thanks, Joris.
On Thu, Oct 31, 2019 at 2:19 PM Dan Smith wrote:
> Hi Szu-Yu Lo,
>
> You should have access now. Thanks for being interested in contributing to
> Geode! If you haven't alre
Thanks Naba - I'll try to adapt :)
On 10/31/19 7:33 PM, Nabarun Nag wrote:
It is how Github branch protection is designed.
This is my explanation from the information provided by you :
- The Pull Request you mentioned had 11 commits and when you tried to
merged it, I assume you tried to squash
Ignore this email, I've previously replied to a thread in the list and I'm
not seeing that reply anywhere, trying to see if it's a general issue or
just a problem with my account.
Cheers.
--
Ju@N
I think it sounds pretty reasonable. Given that the only change to Geode
would be the suggested update to the ClientHello and we shouldn't need to
make any additional changes in order to leverage the functionality.
Presumably the custom Provider would need to be installed by the user and
configured
Hello Alberto,
I'm not particularly knowledgeable on this subject so I might be missing
something, but with Geode you can independently configure SSL for specific
system components, can't you just use multiple alias to achieve your use
case as described here [1]?.
*>> The situation is the followi
I have the same concern so I’d like to see the effort expended to be on making
this pluggable. What in our current implementation needs to change so that
someone can plug in an alternative implementation. The default being what we do
now and the alternative using this extension the way you want.
Juan,
Let me try and answer just to ensure that *I* fully understand the use case.
>From an 'alias' POV this could be seen as having the ability for a *single*
component (locator, server, etc) to have multiple (dynamic) aliases. So,
depending on where the connection originated *from* a particular
Hi Joris,
You now also have access.
Thanks!
-Dan
On Fri, Nov 1, 2019 at 8:12 AM Joris Melchior wrote:
> Hi Dan,
>
> Can you provide me with the ability to assign tickets to myself as well?
>
> Username: joris.melchior
>
> Thanks, Joris.
>
> On Thu, Oct 31, 2019 at 2:19 PM Dan Smith wrote:
>
>
Thanks Dan!
On Fri, Nov 1, 2019 at 3:01 PM Dan Smith wrote:
> Hi Joris,
>
> You now also have access.
>
> Thanks!
> -Dan
>
> On Fri, Nov 1, 2019 at 8:12 AM Joris Melchior
> wrote:
>
> > Hi Dan,
> >
> > Can you provide me with the ability to assign tickets to myself as well?
> >
> > Username: jo
After testing, we're going to upgrade the concourse infrastructure to 5.7.0
this morning. We do not anticipate any issues during this upgrade.
-Sean.
I'm seeing ClassNotFoundExceptions for FQN of the old package of the
LogService:
[locator] Caused by: java.lang.ClassNotFoundException:
*org.apache.geode.internal.logging.LogService*
[locator] at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
The above is interesting because it's the
Hi Sean,
Should I be concerned? I have a bunch of queued up jobs going to test
distributed unit tests.
Thanks,
Mark
> On Nov 1, 2019, at 10:06 AM, Sean Goller wrote:
>
> After testing, we're going to upgrade the concourse infrastructure to 5.7.0
> this morning. We do not anticipate any issue
To reproduce, drop this new test in geode-dunit/src/distributedTest/java
and then run it in IntelliJ or however you want.
It passes, but if you search through the output you'll find the error in my
first message with:
Caused by: java.lang.ClassNotFoundException:
*org.apache.geode.internal.logging
Hi Kirk,
Did you do a ./gradlew clean? It looks like you might be picking up an old
version of one of the geode war files that is referring to the old location
of the LogService class.
-Dan
On Fri, Nov 1, 2019 at 3:28 PM Kirk Lund wrote:
> To reproduce, drop this new test in geode-dunit/src/di
Your test passes for me, btw.
-Dan
On Fri, Nov 1, 2019 at 4:14 PM Dan Smith wrote:
> Hi Kirk,
>
> Did you do a ./gradlew clean? It looks like you might be picking up an old
> version of one of the geode war files that is referring to the old location
> of the LogService class.
>
> -Dan
>
> On F
17 matches
Mail list logo
