Vote for sticking with standard workflow. -- justin
On Aug 26, 2015 12:05 PM, "Ivan Zhakov" wrote:
> On 26 August 2015 at 18:48, Bert Huijben wrote:
> > Ivan,
> >
> > An initial (test?) import has been completed. See
> https://issues.apache.org/jira/browse/SERF/
> >
> I see. It's only t
On Wed, Aug 26, 2015 at 2:52 PM, Ivan Zhakov wrote:
> Status update:
> ASF INFRA team performed test import for us:
> https://issues.apache.org/jira/browse/SERF
Looks good to me! Thanks all! -- justin
Yah, we had the project name for well over a decade before Hashicorp
chose the name for their project. It's caused all sort of confusion
when I tell people about Serf as they think it's the Hashicorp
project.
I just don't think it makes sense to do anything at this point.
Perhaps put a note on th
On Tue, Sep 1, 2015 at 9:03 AM, Ivan Zhakov wrote:
> I think it's a good idea. I also suggest to reconsider decision about
> using dev@s.a.o for commit and JIRA notifications -- it's hard to
> filter them and important dev@ discussions could be missed with
> current approach.
*shrug*
Let's give
On Mon, Aug 29, 2016 at 5:59 AM, Bert Huijben wrote:
> The 1.3.9 release artifacts are now available for testing/signing.
>
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/serf
> and add your signatures there. I plan to try and release on September 1st
> so please try an
On Wed, Aug 31, 2016 at 8:02 AM, Bert Huijben wrote:
> If you still want to add your signature, please commit them to
> https://dist.apache.org/repos/dist/release/serf
I don't know what the process for doing that is any more. Any
pointers? -- justin
We definitely did write and test the OCSP support in Denver. It should
work, but we don't have regression tests for it.
Alas, I won't be in Seville.
Cheers. -- justin
On Oct 26, 2016 4:16 AM, "Lieven Govaerts" wrote:
Hi Branko,
On Tue, Oct 25, 2016 at 5:25 PM, Branko Čibej wrote:
> On 24.
Sounds good to me. I'll try to reserve some cycles to test in the coming
week.
Cheers. -- justin
On Thu, May 3, 2018 at 4:11 PM Branko Čibej wrote:
> I think there are more than enough improvements on trunk[1] to warrant a
> new release; whether that's called 1.4.0 or 2.0 (which is the curren
On Mon, Oct 8, 2018 at 3:37 AM Branko Čibej wrote:
> On 01.10.2018 15:41, Branko Čibej wrote:
> > Hi!
> >
> > I've just committed the 1.4.0 RC1 release artefacts here:
> >
> > https://dist.apache.org/repos/dist/dev/serf
> >
> > Please give them a spin. I don't actually plan to officially release
James,
Thanks for the bug report. For reference, the upstream OpenSSL commit
looks to be:
https://github.com/openssl/openssl/commit/d924dbf4ae127c68463bcbece04b6e06abc58928
I strongly suspect that the patch on our side (against 1.3.x) is something
akin to below. I'm having trouble getting a te
seeing
something different than you (or the builder) are...I'll also try to pull
in your patch set against vanilla 1.3.x to see if I can match the reported
error.
Cheers. -- justin
On Wed, Mar 25, 2020 at 8:17 PM James McCoy wrote:
> On Wed, Mar 25, 2020 at 08:57:14AM -0400, Justin
patches and work my way back towards
upstream.
Cheers. — justin
On Fri, Mar 27, 2020 at 5:27 PM James McCoy wrote:
> On Fri, Mar 27, 2020 at 05:15:24PM -0400, Justin Erenkrantz wrote:
> > James,
> >
> > I finally got a Debian sid environment up. However, I'm seeing a
&g
the libssl1.1-dbgsym package; then I was able
to break on the ssl3_read_n call and see the callstack.
On Fri, Mar 27, 2020 at 5:56 PM Lucas Nussbaum wrote:
> Hi Justin,
>
> Most likely, this is due to the new openssl version in unstable.
>
> Lucas
>
>
> On 27/03/20 at 17:15
R_UNEXPECTED_EOF_WHILE_READING) {
+*len = 0;
+return APR_EOF;
+ }
+ /* Fallthrough */
default:
*len = 0;
serf__log(TEST_VERBOSE, __FILE__,
On Sat, Mar 28, 2020 at 9:49 AM Justin Erenkrantz
wrote:
> Ok
James,
Thanks. I've backported the requisite changes to the 1.3.x branch to
support Python 3.x and scons - I tested on Ubuntu 18.04 and Debian Sid.
(Bert and Andreas had already reviewed those changes.)
In reviewing your Python 3.x patches, I noticed a change to
build/gen_def.py ; in my local te
Hi all!
I hope that everyone is doing as well as they can in these times.
I'd like to do a sweep of STATUS and do a final 1.3.x release that captures
the relevant build system and test fixes. I'll try to test out the Visual
Studio fixes that are pending for 1.3.x; I have VS 2019 here, so I may t
On Tue, Mar 31, 2020 at 2:33 PM Branko Čibej wrote:
> Thanks, Justin. I don't know if we need another 1.3.x release, given
> that 1.4 will be API compatible and has more robust OpenSSL 1.1.x and
> LibreSSL support.
>
My preference would be to just do a small 1.3.x release out with critical
build
On Thu, Apr 2, 2020 at 8:06 AM James McCoy wrote:
> Just as an FYI, the OpenSSL changes have been partially reverted[1]
> upstream for the 1.1.1f release. The change will be re-introduced in
> 3.0, so using the ifdef, instead of OpenSSL version, was the prudent
> choice.
>
Thanks for the update
On Wed, Apr 1, 2020 at 1:10 PM Ivan Zhakov wrote:
> On Tue, 31 Mar 2020 at 23:13, Justin Erenkrantz
> wrote:
> >
> > On Tue, Mar 31, 2020 at 2:33 PM Branko Čibej wrote:
> >
> > > Thanks, Justin. I don't know if we need another 1.3.x release, given
> &g
Johan,
Thanks for the note!
The Python3 patches should already be in 1.3.x branch ready for our next
release. We've also got 2 +1s in STATUS for VS 2017 support for 1.3.x, but
I've yet to be able to confirm it for 2017 myself and also there's now 2019
as well...so, I've held off merging that cha
019), I will certainly try it for my next SVN
> build. I'm subscribed to this list now, so I should be able to see the
> announcement :-).
>
> Thanks for your efforts,
> --
> Johan
>
> On Mon, Apr 20, 2020 at 1:34 PM Justin Erenkrantz
> wrote:
> >
> > Johan,
&g
Thanks. I expect that this might be due to the last change - erroring out
on an expired self-signed root cert. Though I thought we didn’t check in a
root cert for our test chain...could Debian’s packaging be including a cert
for testing?
I will try to take a look this week with Debian sid...I as
lures, expected_failures);
/* We expect an error from the certificate validation function. */
if (failures & expected_failures)
return APR_SUCCESS;
On Sun, Dec 27, 2020 at 11:22 AM James McCoy wrote:
> On Sun, Dec 27, 2020 at 10:46:24AM -0500, Justin Erenkrantz wrote:
&
On Mon, Dec 28, 2020 at 5:00 PM Justin Erenkrantz
wrote:
> It's not clear to me if OpenSSL authors intended to make this breaking
> change. On the serf side, we would need to think through what it would
> mean to have our app callback return false upon failure in order to
>
apr_status_t status;
+
+status = run_client_and_mock_servers_loops(tb, num_requests,
handler_ctx,
+ pool);
+ CuAssertIntEquals_Msg(tc, serf_error_string(status), APR_EGENERAL,
status);
+}
+
void setup_test_mock_server(test_baton_t *tb)
{
void *acceptor_baton,
On Thu, Jan 14, 2021 at 11:35 PM James McCoy wrote:
> Happy New Year!
>
> On Wed, Dec 30, 2020 at 10:39:28PM -0500, James McCoy wrote:
> > On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote:
> > > The OpenSSL d
On Fri, Jan 15, 2021 at 9:13 PM James McCoy wrote:
> On Fri, Jan 15, 2021 at 08:36:22AM -0500, Justin Erenkrantz wrote:
> > Sadly, my Debian sid box ran into other issues and is currently
> inaccessible.
> >
> > I *think* that this would address the 1.3.x test iss
Hi Andrew,
You can pass in the -f and -m options to serf_get to send a POST request -
eg:
% ./serf_get -m POST -f your.json
Take a look around setup_request (lines 347) and the options parsing around
lines 617:
https://github.com/apache/serf/blob/trunk/test/serf_get.c#L347
https://github.com/ap
Thanks for the patch.
Is the release|debug_ a standard CMake output directory or specific
to how TortoiseSVN is building Serf?
Cheers. — justin
On Wed, Jul 21, 2021 at 8:36 AM Daniel Sahlberg
wrote:
> Hi,
>
> TortoiseSVN is importing SERF via a svn:externals definition:
> [[[
> https://svn.ap
Hi Evgeny,
Thanks so much for picking this up! I will aim to do a sweep of STATUS
this weekend and provide votes/reviews for any backports.
And, I will try to carve out some time to help test releases on a few
platforms once we have tarballs ready to go.
Cheers. -- justin
On Wed, May 3, 2023,
On Fri, May 12, 2023 at 7:43 AM Ivan Zhakov wrote:
> On 2023/05/10 11:33:40 Evgeny Kotkov wrote:
> > Evgeny Kotkov writes:
> >
> > > The current state is as follows:
> > >
> > > - I prepared a set of nominated fixes in ^/serf/branches/1.3.x/STATUS.
> > > - Most of them are required for OpenSSL 3
+1 for release.
Confirmed GPG sigs and SHA512 hashes.
Tested on Ubuntu 22.04.2 (has OpenSSL 3). All checks passed.
Of note, I did run into the EADDRINUSE issue on the context checks when
running test_all. I added some debug lines to confirm that's what's going
on, but it does eventually comple
Hi Mirko,
>From your logs, it definitely appears that the client is being rejected for
not presenting the right client certificate with that required DN.
How are you specifying the client cert in Subversion?
Is OpenSSL's s_client able to connect to the server with that client cert
correctly when
supported:../crypto/evp/evp_fetch.c:373:Global
>
> > default library context, Algorithm (RC2-40-CBC : 0), Properties ()
>
> So, I've recreated the pkcs12 file with the command
>
> > openssl pkcs12 -export -in mirko.cert -inkey mirko.chiave -passin
> > file:mirko.
[
https://issues.apache.org/jira/browse/SERF-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208223#comment-17208223
]
Justin Erenkrantz commented on SERF-176:
My initial feeling would be to have
[
https://issues.apache.org/jira/browse/SERF-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214994#comment-17214994
]
Justin Erenkrantz commented on SERF-197:
As of right now, I can't repro
[
https://issues.apache.org/jira/browse/SERF-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215003#comment-17215003
]
Justin Erenkrantz commented on SERF-197:
I chatted with the infra folks over S
[
https://issues.apache.org/jira/browse/SERF-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Erenkrantz resolved SERF-197.
Resolution: Fixed
> Website content starts with U+F
[
https://issues.apache.org/jira/browse/SERF-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215592#comment-17215592
]
Justin Erenkrantz commented on SERF-197:
In chatting further with Infra
[
https://issues.apache.org/jira/browse/SERF-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281137#comment-17281137
]
Justin Erenkrantz commented on SERF-198:
Thanks for the report and patch!
We
[
https://issues.apache.org/jira/browse/SERF-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397742#comment-17397742
]
Justin Erenkrantz commented on SERF-202:
Thanks for the report. We know
[
https://issues.apache.org/jira/browse/SERF-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397746#comment-17397746
]
Justin Erenkrantz commented on SERF-190:
Does applying the attached patch res
42 matches
Mail list logo
