On 29 April 2015 at 20:34, Rafael Schloming r...@alum.mit.edu wrote:
Hi Everyone,
I've put out an RC for 0.9.1 in the usual places.
Source artifacts are here:
https://people.apache.org/~rhs/qpid-proton-0.9.1-rc1/
Java binaries are here:
Robbie Gemmell created PROTON-874:
-
Summary: PN_VERSION only supports major and minor versions
Key: PROTON-874
URL: https://issues.apache.org/jira/browse/PROTON-874
Project: Qpid Proton
On Thu, Apr 30, 2015 at 8:35 AM, Ken Giusti kgiu...@redhat.com wrote:
- Original Message -
From: Rafael Schloming r...@alum.mit.edu
To: proton@qpid.apache.org
Sent: Wednesday, April 29, 2015 4:24:09 PM
Subject: Re: Python 3 port is 'done'
What happens when I run make test
- Original Message -
From: Rafael Schloming r...@alum.mit.edu
To: proton@qpid.apache.org
Sent: Thursday, April 30, 2015 9:00:14 AM
Subject: Re: Python 3 port is 'done'
On Thu, Apr 30, 2015 at 8:35 AM, Ken Giusti kgiu...@redhat.com wrote:
- Original Message -
The versions of the Proton pom files were changed on master yesterday
to 0.10-SNAPSHOT (i.e next-release-SNAPSHOT), from their previous
constant use of 1.0-SNAPSHOT regardless of the next release version.
As a result of this the nightly snapshot job is now publishing with
the new version, which
- Original Message -
From: Rafael Schloming r...@alum.mit.edu
To: proton@qpid.apache.org
Sent: Wednesday, April 29, 2015 4:24:09 PM
Subject: Re: Python 3 port is 'done'
What happens when I run make test and I have both python2 and python3
installed on my system? Do the tests run
[
https://issues.apache.org/jira/browse/PROTON-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-874.
Resolution: Fixed
Fix Version/s: 0.10
PN_VERSION only supports major and
- Original Message -
From: Ken Giusti kgiu...@redhat.com
To: proton@qpid.apache.org
Cc: us...@qpid.apache.org
Sent: Thursday, April 30, 2015 9:18:26 AM
Subject: Re: Python 3 port is 'done'
- Original Message -
From: Rafael Schloming r...@alum.mit.edu
To:
[
https://issues.apache.org/jira/browse/PROTON-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521993#comment-14521993
]
ASF subversion and git services commented on PROTON-865:
Commit
[
https://issues.apache.org/jira/browse/PROTON-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521813#comment-14521813
]
ASF GitHub Bot commented on PROTON-727:
---
GitHub user dcristoloveanu opened a pull
GitHub user dcristoloveanu opened a pull request:
https://github.com/apache/qpid-proton/pull/27
Add some NULL checks and fix some realloc leaks
Along the lines of PROTON-727, added NULL checks for some malloc/realloc
calls that were either ignoring the result or leaking in the case
Can the proton reactor be used to deliver work from multiple connections
to a thread pool, where work from a given connection is only handled by
one thread at a time (so access to each pn_transport and it's stuff is
serialized)? That is a pretty standard model for servers.
It doesn't look to me
Hi Alan,
I've been playing with the reactor a bit, and one of my early thoughts was: how
do
you scale this thing across multiple cores?
The architecture I've worked with before uses (approximately) one selector +
thread
pair per core and balances connections across the selectors. Anything
I'm interested in knowing the timelines the community has in mind for the
0.10 release.
A tentative date for alpha and beta cycles would be helpful in planning the
work tasks and vacation time.
Regards,
Rajith
Failures on Windows (beyond the four SASL failures in PROTON-875) running
Python 2.6.1
37 MessengerTests tests (all that aren't skipped) fail with
Unexpected input while waiting for receiver to initialize: READY
- Original Message -
From: Ken Giusti kgiu...@redhat.com
To:
What sort of work/connections are you talking about here? Are you talking
about processing AMQP messages in a thread pool or are you talking about
writing some sort of multithreaded I/O handler?
--Rafael
On Thu, Apr 30, 2015 at 2:47 PM, Alan Conway acon...@redhat.com wrote:
Can the proton
I'd like to see one fairly soon. I'm currently working through a few
sasl-related interop issues between proton-c and proton-j, but once that is
done and gordon's map fix lands, I think we would be in decent shape to put
out a 0.10 in short order.
--Rafael
On Thu, Apr 30, 2015 at 3:06 PM, Rajith
On 04/29/2015 03:34 PM, Rafael Schloming wrote:
Hi Everyone,
I've put out an RC for 0.9.1 in the usual places.
Source artifacts are here:
https://people.apache.org/~rhs/qpid-proton-0.9.1-rc1/
Java binaries are here:
On 29 April 2015 at 21:05, Ken Giusti kgiu...@redhat.com wrote:
Well, done enough to consider merging to master.
While the patch is quite large, most of the changes are simple syntax changes
to avoid non-python3 compliant syntax.
The code is available on the kgiusti-python3 branch at the
Chuck Rolke created PROTON-875:
--
Summary: Proton-C SASL changes break windows self tests
Key: PROTON-875
URL: https://issues.apache.org/jira/browse/PROTON-875
Project: Qpid Proton
Issue Type:
On 30 April 2015 at 15:56, Ken Giusti kgiu...@redhat.com wrote:
- Original Message -
From: Robbie Gemmell robbie.gemm...@gmail.com
To: proton@qpid.apache.org
Cc: us...@qpid.apache.org
Sent: Thursday, April 30, 2015 10:20:07 AM
Subject: Re: Python 3 port is 'done'
On 29 April 2015
- Original Message -
From: Robbie Gemmell robbie.gemm...@gmail.com
To: proton@qpid.apache.org
Cc: us...@qpid.apache.org
Sent: Thursday, April 30, 2015 10:20:07 AM
Subject: Re: Python 3 port is 'done'
On 29 April 2015 at 21:05, Ken Giusti kgiu...@redhat.com wrote:
Well, done
22 matches
Mail list logo
