[jira] [Created] (PROTON-1307) go binding amqp.message does not honor Inferred flag

Richard Laos created PROTON-1307: Summary: go binding amqp.message does not honor Inferred flag Key: PROTON-1307 URL: https://issues.apache.org/jira/browse/PROTON-1307 Project: Qpid Proton

[jira] [Commented] (QPID-7317) Deadlock on publish

[ https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517632#comment-15517632 ] Alan Conway commented on QPID-7317: --- Not marking resolved yet. The fix above has not been proven to

[jira] [Commented] (QPID-7317) Deadlock on publish

[ https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517624#comment-15517624 ] ASF subversion and git services commented on QPID-7317: --- Commit

[jira] [Commented] (QPID-5637) Python client does not reset the Selector singleton when the process id changes.

[ https://issues.apache.org/jira/browse/QPID-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517625#comment-15517625 ] ASF subversion and git services commented on QPID-5637: --- Commit

[jira] [Resolved] (DISPATCH-523) Topology changes can cause in-flight deliveries to be stuck in the ingress router

[ https://issues.apache.org/jira/browse/DISPATCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-523. --- Resolution: Fixed > Topology changes can cause in-flight deliveries to be stuck in the ingress >

[jira] [Commented] (DISPATCH-523) Topology changes can cause in-flight deliveries to be stuck in the ingress router

[ https://issues.apache.org/jira/browse/DISPATCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517587#comment-15517587 ] ASF subversion and git services commented on DISPATCH-523: -- Commit

[jira] [Created] (DISPATCH-523) Topology changes can cause in-flight deliveries to be stuck in the ingress router

Ted Ross created DISPATCH-523: - Summary: Topology changes can cause in-flight deliveries to be stuck in the ingress router Key: DISPATCH-523 URL: https://issues.apache.org/jira/browse/DISPATCH-523

[jira] [Updated] (QPID-7435) Avoid BDB fetching dummy single byte database entries during message instance recovery

[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7435: - Summary: Avoid BDB fetching dummy single byte database entries during message instance recovery (was:

[jira] [Updated] (QPID-7435) Avoid BDB fetching empty database entry during message instance recovery

[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7435: - Status: Reviewable (was: In Progress) > Avoid BDB fetching empty database entry during message instance

[jira] [Assigned] (QPID-7435) Avoid BDB fetching empty database entry during message instance recovery

[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7435: Assignee: Keith Wall > Avoid BDB fetching empty database entry during message instance recovery >

[jira] [Commented] (QPID-7435) Avoid BDB fetching empty database entry during message instance recovery

[ https://issues.apache.org/jira/browse/QPID-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516889#comment-15516889 ] ASF subversion and git services commented on QPID-7435: --- Commit 1762070 from

[jira] [Created] (QPID-7435) Avoid BDB fetching empty database entry during message instance recovery

Keith Wall created QPID-7435: Summary: Avoid BDB fetching empty database entry during message instance recovery Key: QPID-7435 URL: https://issues.apache.org/jira/browse/QPID-7435 Project: Qpid

Re: ctest nit: rename cpp and go tests.

+1 The presumption is that you are referring to qpid-proton tests and not qpid-cpp or qpid-dispatch or ... The widest ranging test is 'python-test'. This could be renamed to 'proton-tests-of-all-sorts-using-python-test-framework'. When you run python-test all the test logs print

Re: ctest nit: rename cpp and go tests.

Yes, please. On Fri, Sep 23, 2016 at 8:33 AM, Alan Conway wrote: > I'd like to rename the C++ and Go tests to use "-" instead of "_" so > they are consistent with the other tests. This is my fault, I wasn't > paying attention when I added the tests. The original tests are

ctest nit: rename cpp and go tests.

I'd like to rename the C++ and Go tests to use "-" instead of "_" so they are consistent with the other tests. This is my fault, I wasn't paying attention when I added the tests. The original tests are like:   Test  #2: python-test   Test  #5: ruby-spec-test   Test #16: c-object-tests The

[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost

[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516682#comment-15516682 ] Keith Wall commented on QPID-7379: -- End to end test case added verifying a message store containing a

[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost

[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1551#comment-1551 ] ASF subversion and git services commented on QPID-7379: --- Commit 1762067 from

[GitHub] qpid-dispatch pull request #103: DISPATCH-521 - Added a version command line...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/103 DISPATCH-521 - Added a version command line option that will display … …the version of the dispatch router You can merge this pull request into a Git repository by running: $

[jira] [Commented] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516574#comment-15516574 ] ASF GitHub Bot commented on DISPATCH-521: - GitHub user ganeshmurthy opened a pull request:

[jira] [Commented] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516563#comment-15516563 ] Ganesh Murthy commented on DISPATCH-521: IMHO, the --version should simply put out the version

[jira] [Commented] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516511#comment-15516511 ] Jiri Danek commented on DISPATCH-521: - True, that. Regarding the future of this issue, it all

[jira] [Commented] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516417#comment-15516417 ] Ted Ross commented on DISPATCH-521: --- >>Running just qdrouterd is not sufficient, because port 5672 may

[jira] [Comment Edited] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515979#comment-15515979 ] Keith Wall edited comment on QPID-7366 at 9/23/16 10:21 AM: Rob - can you

[jira] [Comment Edited] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515975#comment-15515975 ] Keith Wall edited comment on QPID-7366 at 9/23/16 9:57 AM: --- I've made some

[jira] [Created] (QPID-7434) Mature the AMQP message conversion layer

Keith Wall created QPID-7434: Summary: Mature the AMQP message conversion layer Key: QPID-7434 URL: https://issues.apache.org/jira/browse/QPID-7434 Project: Qpid Issue Type: Improvement

[jira] [Commented] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515979#comment-15515979 ] Keith Wall commented on QPID-7366: -- Rob - can you review and ensure that this is an acceptable compromise

[jira] [Commented] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515975#comment-15515975 ] Keith Wall commented on QPID-7366: -- I've made some hopefully reasonable pragmatic changes to

[jira] [Commented] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515971#comment-15515971 ] ASF subversion and git services commented on QPID-7366: --- Commit 1762041 from

[jira] [Updated] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7366: - Assignee: Rob Godfrey (was: Keith Wall) > [Java Broker] Add Management operation to VirtualHost to allow

[jira] [Updated] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7366: - Status: Reviewable (was: In Progress) > [Java Broker] Add Management operation to VirtualHost to allow

Proton 14's Ruby bindings require rubygem-rspec and rubygem-simplecov, even without testing

Could you please add dependencies: rubygem-rspec rubygem-simplecov for Fedora 24 at least, to the installation documentation?

[jira] [Comment Edited] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513665#comment-15513665 ] Keith Wall edited comment on QPID-7366 at 9/23/16 8:05 AM: --- Currently, the new

[jira] [Comment Edited] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513665#comment-15513665 ] Keith Wall edited comment on QPID-7366 at 9/23/16 8:04 AM: --- Currently, the new