Re: [VOTE] Release Qpid Proton 0.12.2

+1 - just verified that the change to the version in python. Since there are no python-related changes (other than the fix version), I'll likely skip pushing this up to Pypi (unless there is a general call to do so). - Original Message - > From: "Robbie Gemmell"

[jira] [Created] (PROTON-1172) Bump the priority of reactor 'connecting' log messages down to Debug

Ken Giusti created PROTON-1172: -- Summary: Bump the priority of reactor 'connecting' log messages down to Debug Key: PROTON-1172 URL: https://issues.apache.org/jira/browse/PROTON-1172 Project: Qpid

Re: [VOTE] merge the proton mailing list into the users/dev lists

+1 - Original Message - > From: "Robbie Gemmell" > To: us...@qpid.apache.org, proton@qpid.apache.org > Sent: Wednesday, March 30, 2016 6:25:34 AM > Subject: [VOTE] merge the proton mailing list into the users/dev lists > > Hello folks, > > Many moons ago, a seperate

Re: Does anyone read this list?

+1 to nuking proton@ from orbit. - Original Message - > From: "Fraser Adams" > To: proton@qpid.apache.org > Sent: Friday, March 25, 2016 2:52:02 AM > Subject: Re: Does anyone read this list? > > +1 on Alan's comments > > Qpid has lots of components and a

[jira] [Assigned] (PROTON-1133) Proton C includes port number in AMQP Open hostname

[ https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1133: -- Assignee: Ken Giusti > Proton C includes port number in AMQP Open hostn

[jira] [Resolved] (PROTON-1087) Building the library without the required SSL dependencies silently doesn't use SSL for AMQPS

[ https://issues.apache.org/jira/browse/PROTON-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1087. Resolution: Fixed Fix Version/s: 0.12.1 I believe the PROTON-1157 fix applies here as well

[jira] [Resolved] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.

[ https://issues.apache.org/jira/browse/PROTON-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1157. Resolution: Fixed Assignee: Ken Giusti (was: Gordon Sim) > Reactor sends messa

[jira] [Commented] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.

[ https://issues.apache.org/jira/browse/PROTON-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187936#comment-15187936 ] Ken Giusti commented on PROTON-1157: Reviewboard: https://reviews.apache.org/r/44591/ > Reac

[jira] [Created] (PROTON-1157) Reactor sends messages in the clear if ssl is requested by not available.

Ken Giusti created PROTON-1157: -- Summary: Reactor sends messages in the clear if ssl is requested by not available. Key: PROTON-1157 URL: https://issues.apache.org/jira/browse/PROTON-1157 Project: Qpid

[jira] [Resolved] (PROTON-1150) Python setup.py fails to use environment settings

[ https://issues.apache.org/jira/browse/PROTON-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1150. Resolution: Fixed > Python setup.py fails to use environment setti

[jira] [Commented] (PROTON-1150) Python setup.py fails to use environment settings

[ https://issues.apache.org/jira/browse/PROTON-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175679#comment-15175679 ] Ken Giusti commented on PROTON-1150: Ooopsie - I pulled Robert's fix but failed to add the 'PROTON

[jira] [Created] (PROTON-1150) Python setup.py fails to use environment settings

Ken Giusti created PROTON-1150: -- Summary: Python setup.py fails to use environment settings Key: PROTON-1150 URL: https://issues.apache.org/jira/browse/PROTON-1150 Project: Qpid Proton Issue

Re: Proton-J Reactor sending delay

Andrew - are you calling send() from within a reactor callback? Or from another thread? I'm not very familiar with the Java reactor, but the C reactor has a method called pn_reactor_wakeup() which causes it to immediately return from the blocking select() call. -K - Original Message

[jira] [Commented] (PROTON-1133) Proton C includes port number in AMQP Open hostname

[ https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159022#comment-15159022 ] Ken Giusti commented on PROTON-1133: This issue is caused by a defect in the way Reactor obtains

[jira] [Updated] (PROTON-1133) Proton C includes port number in AMQP Open hostname

[ https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1133: --- Fix Version/s: 0.13.0 0.12.1 Component/s: python-binding

[jira] [Updated] (PROTON-1133) Proton C includes port number in AMQP Open hostname

[ https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1133: --- Fix Version/s: (was: 0.12.1) > Proton C includes port number in AMQP Open hostn

Re: Dropping proton-dump; Moving to newer minimum CMake version

- Original Message - > From: "Andrew Stitcher" > To: "proton" , "Qpid Developers" > > Sent: Monday, February 15, 2016 5:03:40 PM > Subject: Dropping proton-dump; Moving to newer minimum CMake version > > I've been

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

+1 for releasing RC3 - Original Message - > From: "Justin Ross" > To: us...@qpid.apache.org, proton@qpid.apache.org > Sent: Wednesday, February 10, 2016 9:04:03 AM > Subject: [VOTE] Release RC 3 as Qpid Proton 0.12.0 > > Hi, everyone. RC 2 had some embedded

Re: [VOTE] Release Qpid Proton 0.12.0

+1 release 0.12.0 RC bits as 0.12.0 GA tested on Centos7: - unit test and install - verified pyngus 2.0.3 unit tests and examples pass - verified mainline oslo.messaging functional tests pass - verified mainline rsyslog amqp1 plugin functions - Original Message - > From: "Justin

[jira] [Updated] (PROTON-1123) cmake fails under python3 when -DSYSINSTALL_BINDINGS=ON

[ https://issues.apache.org/jira/browse/PROTON-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1123: --- Fix Version/s: 0.12.0 > cmake fails under python3 when -DSYSINSTALL_BINDI

[jira] [Commented] (PROTON-1121) Zero pointer derefence in pn_sasl_allowed_mechs()

[ https://issues.apache.org/jira/browse/PROTON-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129031#comment-15129031 ] Ken Giusti commented on PROTON-1121: I've reviewed the patch and it looks fine for 0.12.0 inclusion

[jira] [Updated] (PROTON-1118) python setup.py build fails if run from git repo

[ https://issues.apache.org/jira/browse/PROTON-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1118: --- Fix Version/s: 0.12.0 > python setup.py build fails if run from git r

[jira] [Created] (PROTON-1123) cmake fails under python3 when -DSYSINSTALL_BINDINGS=ON

Ken Giusti created PROTON-1123: -- Summary: cmake fails under python3 when -DSYSINSTALL_BINDINGS=ON Key: PROTON-1123 URL: https://issues.apache.org/jira/browse/PROTON-1123 Project: Qpid Proton

[jira] [Assigned] (PROTON-1123) cmake fails under python3 when -DSYSINSTALL_BINDINGS=ON

[ https://issues.apache.org/jira/browse/PROTON-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1123: -- Assignee: Ken Giusti > cmake fails under python3 when -DSYSINSTALL_BINDI

[jira] [Updated] (PROTON-1099) Upload latest stable release of python-qpid-proton onto pypi

[ https://issues.apache.org/jira/browse/PROTON-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1099: --- Priority: Major (was: Blocker) > Upload latest stable release of python-qpid-proton onto p

[jira] [Resolved] (PROTON-1118) python setup.py build fails if run from git repo

[ https://issues.apache.org/jira/browse/PROTON-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1118. Resolution: Fixed > python setup.py build fails if run from git r

[jira] [Updated] (PROTON-1118) python setup.py build fails if run from git repo

[ https://issues.apache.org/jira/browse/PROTON-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1118: --- Fix Version/s: (was: 0.12.0) 0.13.0 > python setup.py build fails if run f

[jira] [Commented] (PROTON-1120) Memory leak using proton.utils

[ https://issues.apache.org/jira/browse/PROTON-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15127614#comment-15127614 ] Ken Giusti commented on PROTON-1120: I approve this patch for inclusion into 0.12.0. > Memory l

[jira] [Created] (PROTON-1118) python setup.py build fails if run from git repo

Ken Giusti created PROTON-1118: -- Summary: python setup.py build fails if run from git repo Key: PROTON-1118 URL: https://issues.apache.org/jira/browse/PROTON-1118 Project: Qpid Proton Issue

[jira] [Assigned] (PROTON-1118) python setup.py build fails if run from git repo

[ https://issues.apache.org/jira/browse/PROTON-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1118: -- Assignee: Ken Giusti > python setup.py build fails if run from git r

[jira] [Commented] (PROTON-1111) Fix warnings during make doc

[ https://issues.apache.org/jira/browse/PROTON-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15119755#comment-15119755 ] Ken Giusti commented on PROTON-: Hrm... not sure why this change was made: -from . import

[jira] [Resolved] (PROTON-1104) reactor hangs on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1104. Resolution: Fixed > reactor hangs on reconn

[jira] [Updated] (PROTON-1104) reactor hangs on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1104: --- Attachment: testcase.c Reproducer. > reactor hangs on reconn

[jira] [Commented] (PROTON-1104) reactor hangs on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114571#comment-15114571 ] Ken Giusti commented on PROTON-1104: Reviewboard: https://reviews.apache.org/r/42700/ > reac

[jira] [Updated] (PROTON-1104) reactor hangs on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1104: --- Affects Version/s: 0.10 > reactor hangs on reconn

[jira] [Resolved] (PROTON-1086) Release 11.1 and following versions on PyPI

[ https://issues.apache.org/jira/browse/PROTON-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1086. Resolution: Fixed Fix Version/s: 0.11.1 0.11.1 is now available on pypi > Release 1

[jira] [Created] (PROTON-1099) Upload latest stable release of python-qpid-proton onto pypi

Ken Giusti created PROTON-1099: -- Summary: Upload latest stable release of python-qpid-proton onto pypi Key: PROTON-1099 URL: https://issues.apache.org/jira/browse/PROTON-1099 Project: Qpid Proton

[jira] [Resolved] (PROTON-1090) BlockingConnection client spins at 100% cpu on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1090. Resolution: Fixed Assignee: Gordon Sim Validated Gordon's change - fix submitted

[jira] [Assigned] (PROTON-1086) Release 11.1 and following versions on PyPI

[ https://issues.apache.org/jira/browse/PROTON-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1086: -- Assignee: Ken Giusti > Release 11.1 and following versions on P

[jira] [Created] (PROTON-1090) BlockingConnection client spins at 100% cpu on reconnect

Ken Giusti created PROTON-1090: -- Summary: BlockingConnection client spins at 100% cpu on reconnect Key: PROTON-1090 URL: https://issues.apache.org/jira/browse/PROTON-1090 Project: Qpid Proton

[jira] [Updated] (PROTON-1090) BlockingConnection client spins at 100% cpu on reconnect

[ https://issues.apache.org/jira/browse/PROTON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1090: --- Attachment: cputest.py reproducer let it connect to qdrouterd, then restart qdrouterd

[jira] [Created] (PROTON-1071) EventInjector hangs on Windows

Ken Giusti created PROTON-1071: -- Summary: EventInjector hangs on Windows Key: PROTON-1071 URL: https://issues.apache.org/jira/browse/PROTON-1071 Project: Qpid Proton Issue Type: Bug

[jira] [Resolved] (PROTON-1056) Attempting to print an ApplicationEvent raises a NameError

[ https://issues.apache.org/jira/browse/PROTON-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1056. Resolution: Fixed > Attempting to print an ApplicationEvent raises a NameEr

[jira] [Resolved] (PROTON-1001) Python tests fail in environments without unittest2

[ https://issues.apache.org/jira/browse/PROTON-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1001. Resolution: Fixed Fix Version/s: 0.11 > Python tests fail in environments without unitte

[jira] [Created] (PROTON-1056) Attempting to print an ApplicationEvent raises a NameError

Ken Giusti created PROTON-1056: -- Summary: Attempting to print an ApplicationEvent raises a NameError Key: PROTON-1056 URL: https://issues.apache.org/jira/browse/PROTON-1056 Project: Qpid Proton

[jira] [Created] (PROTON-1049) Reactor needs an alternative to using the URL to pass user authentication information.

Ken Giusti created PROTON-1049: -- Summary: Reactor needs an alternative to using the URL to pass user authentication information. Key: PROTON-1049 URL: https://issues.apache.org/jira/browse/PROTON-1049

[jira] [Assigned] (PROTON-1003) ssl transport layer does not define an error handler

[ https://issues.apache.org/jira/browse/PROTON-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1003: -- Assignee: Gordon Sim (was: Ken Giusti) Gordon - see previous comment. Appears

[jira] [Comment Edited] (PROTON-1003) ssl transport layer does not define an error handler

[ https://issues.apache.org/jira/browse/PROTON-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986112#comment-14986112 ] Ken Giusti edited comment on PROTON-1003 at 11/2/15 9:45 PM: - Gordon - see

[jira] [Created] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4

Ken Giusti created PROTON-1032: -- Summary: Cannot call super() on classes derived from Exception in 2.4 Key: PROTON-1032 URL: https://issues.apache.org/jira/browse/PROTON-1032 Project: Qpid Proton

[jira] [Commented] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4

[ https://issues.apache.org/jira/browse/PROTON-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980638#comment-14980638 ] Ken Giusti commented on PROTON-1032: https://reviews.apache.org/r/39759/ > Cannot call su

[jira] [Created] (PROTON-1033) Update the revision of the libqpid-proton library to 4

Ken Giusti created PROTON-1033: -- Summary: Update the revision of the libqpid-proton library to 4 Key: PROTON-1033 URL: https://issues.apache.org/jira/browse/PROTON-1033 Project: Qpid Proton

[jira] [Resolved] (PROTON-1031) [python] Bump the module version to 0.11.0

[ https://issues.apache.org/jira/browse/PROTON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1031. Resolution: Fixed Fix Version/s: 0.12.0 > [python] Bump the module version to 0.1

[jira] [Resolved] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4

[ https://issues.apache.org/jira/browse/PROTON-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1032. Resolution: Fixed Fix Version/s: 0.9.1 Not actually fixed in 0.9.1, but there was no "

[jira] [Updated] (PROTON-1003) ssl transport layer does not define an error handler

[ https://issues.apache.org/jira/browse/PROTON-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1003: --- Fix Version/s: 0.11 > ssl transport layer does not define an error hand

[jira] [Resolved] (PROTON-1029) Do not fail hard if strerror_r fails.

[ https://issues.apache.org/jira/browse/PROTON-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1029. Resolution: Fixed > Do not fail hard if strerror_r fa

[jira] [Commented] (PROTON-905) Long-lived connections leak sessions and links

[ https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978548#comment-14978548 ] Ken Giusti commented on PROTON-905: --- I think that we should bump this off until post 0.11 and bump

[jira] [Created] (PROTON-1029) Do not fail hard if strerror_r fails.

Ken Giusti created PROTON-1029: -- Summary: Do not fail hard if strerror_r fails. Key: PROTON-1029 URL: https://issues.apache.org/jira/browse/PROTON-1029 Project: Qpid Proton Issue Type: Bug

[jira] [Created] (PROTON-1010) BlockingConnection leaks sockets after close() is called

Ken Giusti created PROTON-1010: -- Summary: BlockingConnection leaks sockets after close() is called Key: PROTON-1010 URL: https://issues.apache.org/jira/browse/PROTON-1010 Project: Qpid Proton

[jira] [Closed] (PROTON-1000) Connection leak on heartbeat-timeouted connections

[ https://issues.apache.org/jira/browse/PROTON-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti closed PROTON-1000. -- Resolution: Fixed Reactor is not properly cleaning up the underlying socket. > Connection l

[jira] [Updated] (PROTON-1010) BlockingConnection leaks sockets after close() is called

[ https://issues.apache.org/jira/browse/PROTON-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1010: --- Attachment: pavel.py Pavel's reproducer. Remove the comment on 'self.conn.run()' and the sockets

[jira] [Assigned] (PROTON-1006) Sending pre-settled messages over the python blocking api waits indefinetly

[ https://issues.apache.org/jira/browse/PROTON-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1006: -- Assignee: Gordon Sim > Sending pre-settled messages over the python blocking api wa

[jira] [Resolved] (PROTON-1003) ssl transport layer does not define an error handler

[ https://issues.apache.org/jira/browse/PROTON-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1003. Resolution: Fixed Pushed Gordon's fix. > ssl transport layer does not define an error hand

[jira] [Assigned] (PROTON-1001) Python tests fail in environments without unittest2

[ https://issues.apache.org/jira/browse/PROTON-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1001: -- Assignee: Ken Giusti > Python tests fail in environments without unitte

Re: Qpid Proton pn_data_put_ubyte crash updating pn_message_properties data

Hi Frank, Sounds like it may be this bug: https://issues.apache.org/jira/browse/PROTON-892 what is the value of data->capacity when the pni_data_grow method is called? -K - Original Message - > From: "Frank Quinn" > To: proton@qpid.apache.org > Sent: Tuesday,

[jira] [Resolved] (PROTON-987) Do not assume clock_gettime is available - use system default if not.

[ https://issues.apache.org/jira/browse/PROTON-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-987. --- Resolution: Fixed > Do not assume clock_gettime is available - use system defa

Re: Changing master to always use x.y.z format versions

A big +1 to this. I've always felt semantic versioning makes good sense: http://semver.org/ - Original Message - > From: "Robbie Gemmell" > To: proton@qpid.apache.org > Sent: Friday, September 4, 2015 3:26:59 PM > Subject: Changing master to always use x.y.z

[jira] [Created] (PROTON-987) Do not assume clock_gettime is available - use system default if not.

Ken Giusti created PROTON-987: - Summary: Do not assume clock_gettime is available - use system default if not. Key: PROTON-987 URL: https://issues.apache.org/jira/browse/PROTON-987 Project: Qpid Proton

Re: A case in favor of separate repos for language bindings

While I'm in favor of breaking out the bindings (actually, I'd like to see wider changes to the overall structure of proton, specifically proton-c. But I won't thread-jack - I'll start a separate thread). However - I think the python binding is the one binding where it may not be practical,

[jira] [Created] (PROTON-985) Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock time

Ken Giusti created PROTON-985: - Summary: Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock time Key: PROTON-985 URL: https://issues.apache.org/jira/browse/PROTON-985 Project

[jira] [Resolved] (PROTON-109) Proton should handle inbound max-frame size violations.

[ https://issues.apache.org/jira/browse/PROTON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-109. --- Resolution: Fixed Fix Version/s: 0.10 Proton should handle inbound max-frame size violations

[jira] [Resolved] (PROTON-976) pn_read_frame does not validate frame offset

[ https://issues.apache.org/jira/browse/PROTON-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-976. --- Resolution: Fixed pn_read_frame does not validate frame offset

[jira] [Commented] (PROTON-975) crash occurs if buffer containing outcome and first encrypted frame is received

[ https://issues.apache.org/jira/browse/PROTON-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659925#comment-14659925 ] Ken Giusti commented on PROTON-975: --- Ah, thanks robbie I missed that. crash occurs

[jira] [Created] (PROTON-975) crash occurs if buffer containing outcome and first encrypted frame is received

Ken Giusti created PROTON-975: - Summary: crash occurs if buffer containing outcome and first encrypted frame is received Key: PROTON-975 URL: https://issues.apache.org/jira/browse/PROTON-975 Project

Re: 0.10 beta2?

Hi Robbie - It doesn't look like there are any open blockers for 0.10. Can we branch 0.10 and put out release candidate 1? Here is the list of open JIRAs targetting 0.10: Bug PROTON-969 Cyrus SASL module calls sasl_server_init once for every incoming connection Bug PROTON-950

[jira] [Resolved] (PROTON-953) Travis CI tox tests fail to correctly build python 2.6 extension lib

[ https://issues.apache.org/jira/browse/PROTON-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-953. --- Resolution: Fixed Travis CI tox tests fail to correctly build python 2.6 extension lib

[jira] [Resolved] (PROTON-951) Make install fails when building Proton-C with python 3.4

[ https://issues.apache.org/jira/browse/PROTON-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-951. --- Resolution: Fixed Make install fails when building Proton-C with python 3.4

[jira] [Commented] (PROTON-961) messenger doesn't handle multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645998#comment-14645998 ] Ken Giusti commented on PROTON-961: --- Thanks for the analysis - I agree that Gordon's fix

Re: proton 0.10 blocker

Awww crap. Let's revert the whole thing then. I always felt that 'fix' was more voodoo than science. IMHO I don't think the original bug should be a blocker for 0.10. IIRC it isn't a regression, and there's a 'work around' by using proton events. - Original Message - From: Gordon

[jira] [Resolved] (PROTON-923) [SASL] PN_TRANSPORT_ERROR event not raised

[ https://issues.apache.org/jira/browse/PROTON-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-923. --- Resolution: Fixed Re-tested with 0.10 Beta1 and concur - the TRANSPORT_ERROR event is now properly

Re: proton 0.10 blocker

PROTON-905 reverted. - Original Message - From: Ken Giusti kgiu...@redhat.com To: proton@qpid.apache.org Cc: d...@qpid.apache.org Sent: Tuesday, July 28, 2015 10:49:20 AM Subject: Re: proton 0.10 blocker Awww crap. Let's revert the whole thing then. I always felt that 'fix

[jira] [Commented] (PROTON-961) messenger doesn't handle multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642853#comment-14642853 ] Ken Giusti commented on PROTON-961: --- From my understanding of the code, I'd think your

[jira] [Commented] (PROTON-961) messenger doesn't handle multi-frame transfers

[ https://issues.apache.org/jira/browse/PROTON-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643071#comment-14643071 ] Ken Giusti commented on PROTON-961: --- Let me retract that - this isn't the correct fix

[jira] [Resolved] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so

[ https://issues.apache.org/jira/browse/PROTON-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-958. --- Resolution: Fixed [python] pip installed binding fails to find correct libqpid-proton.so

[jira] [Closed] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython

[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti closed PROTON-952. - Resolution: Won't Fix Have confirmed this is a cmake bug when run under virtualenv. Upgraded cmake

[jira] [Commented] (PROTON-952) Building Proton with python 2.6 and python 3.4 on Travis CI finds and links wrong libpython

[ https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643205#comment-14643205 ] Ken Giusti commented on PROTON-952: --- I'm fairly certain this is a cmake bug

[jira] [Commented] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so

[ https://issues.apache.org/jira/browse/PROTON-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639440#comment-14639440 ] Ken Giusti commented on PROTON-958: --- Reviewboard link: https://reviews.apache.org/r

Re: 0.10 beta1

to the problem: https://reviews.apache.org/r/36744/ - Original Message - From: Ken Giusti kgiu...@redhat.com To: proton@qpid.apache.org Sent: Wednesday, July 22, 2015 4:36:54 PM Subject: Re: 0.10 beta1 I've also took it for a spin: Built/unitests/installed on my Fedora20 box. Built

[jira] [Assigned] (PROTON-943) Bump library (.so) major version for proton-c libraries

[ https://issues.apache.org/jira/browse/PROTON-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-943: - Assignee: Ken Giusti Bump library (.so) major version for proton-c libraries

[jira] [Closed] (PROTON-476) Support a user-context for SASL and SSL objects.

[ https://issues.apache.org/jira/browse/PROTON-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti closed PROTON-476. - Resolution: Won't Fix Fix Version/s: (was: 0.9) Probably no longer necessary - the new

Re: New python tox tests failing on fedora 22, Python 2.7.10/3.4.2

- Original Message - From: aconway acon...@redhat.com To: proton proton@qpid.apache.org Sent: Friday, July 10, 2015 10:01:14 AM Subject: New python tox tests failing on fedora 22, Python 2.7.10/3.4.2 Anyone seeing errors like this? I think the ERROR: InterpreterNotFound should be

[jira] [Created] (PROTON-941) pn_transport_set_server should fail if invoked after binding.

Ken Giusti created PROTON-941: - Summary: pn_transport_set_server should fail if invoked after binding. Key: PROTON-941 URL: https://issues.apache.org/jira/browse/PROTON-941 Project: Qpid Proton

[jira] [Commented] (PROTON-941) pn_transport_set_server should fail if invoked after binding.

[ https://issues.apache.org/jira/browse/PROTON-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622519#comment-14622519 ] Ken Giusti commented on PROTON-941: --- Yeah, hit this in qpid-dispatch (C code). Never

Re: Proton Devs using Linux: please run the python-tox-test unit tests!!

? --Rafael That's a great idea - I'll see to it. On Wed, Jul 8, 2015 at 7:48 AM, Ken Giusti kgiu...@redhat.com wrote: Devs, As you probably know, I've pushed changes to the proton python bindings that make proton compatible with python3. Since then, I've hit bugs in the python3 stuff

Re: Proton Devs using Linux: please run the python-tox-test unit tests!!

July 2015 at 18:30, Dominic Evans dominic.ev...@uk.ibm.com wrote: I do have an unpushed change that partially enables it for travis. I'll push later tonight. On 8 Jul 2015, at 18:27, Ken Giusti kgiu...@redhat.com wrote: Good point, I'll see what I can do on that front

[jira] [Created] (PROTON-939) [SSL] Regression: binding a transport erases the configured peer name

Ken Giusti created PROTON-939: - Summary: [SSL] Regression: binding a transport erases the configured peer name Key: PROTON-939 URL: https://issues.apache.org/jira/browse/PROTON-939 Project: Qpid Proton

Proton Devs using Linux: please run the python-tox-test unit tests!!

Devs, As you probably know, I've pushed changes to the proton python bindings that make proton compatible with python3. Since then, I've hit bugs in the python3 stuff that could've been caught by running the above unit test on a linux system that has python3 installed. This test currently

Re: Proton Devs using Linux: please run the python-tox-test unit tests!!

2015 at 15:48, Ken Giusti kgiu...@redhat.com wrote: Devs, As you probably know, I've pushed changes to the proton python bindings that make proton compatible with python3. Since then, I've hit bugs in the python3 stuff that could've been caught by running the above unit test

[jira] [Resolved] (PROTON-939) [SSL] Regression: binding a transport erases the configured peer name

[ https://issues.apache.org/jira/browse/PROTON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-939. --- Resolution: Fixed [SSL] Regression: binding a transport erases the configured peer name

Re: 0.10 alpha1

Yay Rafi! Thanks! A simple query of currently outstanding blocker JIRAs affecting 0.9+ shows only three: https://issues.apache.org/jira/browse/PROTON-826 (unassigned) https://issues.apache.org/jira/browse/PROTON-923 (asticher) https://issues.apache.org/jira/browse/PROTON-934 (rschloming)

Schedule for the 0.10 release?

Hi all, I remember recently that there was a rumor that we may be able to start the release of 0.10 at the end of june. Now that my july 4th long weekend has worn off - what's left to be done before we can cut an alpha? -- -K

  1   2   3   4   5   >