[jira] [Commented] (PROTON-2782) golang binding build fails
[
https://issues.apache.org/jira/browse/PROTON-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796351#comment-17796351
]
Jiri Daněk commented on PROTON-2782:
This is already fixed on main. There isn't yet a release containing the fixed
code. That will be PROTON-2710
> golang binding build fails
> --
>
> Key: PROTON-2782
> URL: https://issues.apache.org/jira/browse/PROTON-2782
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Martin
>Priority: Major
>
>
> Build of the golang binding fails with Go 1.21 with "cannot define new
> methods on non-local type C.pn_type_t".
> {code:java}
> [root@tripleo-standalone qpid-proton-0.39.0]# cmake -B ./BLD -S $PWD
> -- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
> -- Could NOT find CyrusSASL (missing: CyrusSASL_LIBRARY CyrusSASL_INCLUDE_DIR)
> -- Build type is "RelWithDebInfo" (has debug symbols)
> -- PN_VERSION: 0.39.0 ()
> -- Building the epoll proactor
> -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
> CMake Warning at c/tests/CMakeLists.txt:142 (message):
> No C++ compiler, some C library tests were not built
> -- Found Go: /usr/bin/go (go version go1.21.3 linux/amd64) (1.21).
> -- Configuring done (0.4s)
> -- Generating done (0.0s)
> -- Build files have been written to:
> /root/golang-qpid-apache/qpid-proton-0.39.0/BLD
> [root@tripleo-standalone qpid-proton-0.39.0]# cd BLD/
> [root@tripleo-standalone BLD]# make go-build
> [ 0%] Built target go-mod-link
> [ 9%] Built target generated_c_files
> [ 97%] Built target qpid-proton-core-objects
> [100%] Built target qpid-proton-core
> [100%] Built target go-pkg-link
> # github.com/apache/qpid-proton/go/pkg/amqp
> go/pkg/amqp/types.go:32:9: cannot define new methods on non-local type
> C.pn_type_t
> go/pkg/amqp/unmarshal.go:729:13: cannot define new methods on non-local type
> *C.pn_data_t
> go/pkg/amqp/unmarshal.go:730:13: cannot define new methods on non-local type
> *C.pn_data_t
> go/pkg/amqp/unmarshal.go:731:13: cannot define new methods on non-local type
> *C.pn_data_t
> make[3]: *** [go/CMakeFiles/go-build.dir/build.make:70:
> go/CMakeFiles/go-build] Error 1
> make[2]: *** [CMakeFiles/Makefile2:1634: go/CMakeFiles/go-build.dir/all]
> Error 2
> make[1]: *** [CMakeFiles/Makefile2:1641: go/CMakeFiles/go-build.dir/rule]
> Error 2
> make: *** [Makefile:842: go-build] Error 2
> [root@tripleo-standalone BLD]# {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2782) golang binding build fails
[
https://issues.apache.org/jira/browse/PROTON-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk closed PROTON-2782.
--
Resolution: Duplicate
> golang binding build fails
> --
>
> Key: PROTON-2782
> URL: https://issues.apache.org/jira/browse/PROTON-2782
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Martin
>Priority: Major
>
>
> Build of the golang binding fails with Go 1.21 with "cannot define new
> methods on non-local type C.pn_type_t".
> {code:java}
> [root@tripleo-standalone qpid-proton-0.39.0]# cmake -B ./BLD -S $PWD
> -- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
> -- Could NOT find CyrusSASL (missing: CyrusSASL_LIBRARY CyrusSASL_INCLUDE_DIR)
> -- Build type is "RelWithDebInfo" (has debug symbols)
> -- PN_VERSION: 0.39.0 ()
> -- Building the epoll proactor
> -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
> CMake Warning at c/tests/CMakeLists.txt:142 (message):
> No C++ compiler, some C library tests were not built
> -- Found Go: /usr/bin/go (go version go1.21.3 linux/amd64) (1.21).
> -- Configuring done (0.4s)
> -- Generating done (0.0s)
> -- Build files have been written to:
> /root/golang-qpid-apache/qpid-proton-0.39.0/BLD
> [root@tripleo-standalone qpid-proton-0.39.0]# cd BLD/
> [root@tripleo-standalone BLD]# make go-build
> [ 0%] Built target go-mod-link
> [ 9%] Built target generated_c_files
> [ 97%] Built target qpid-proton-core-objects
> [100%] Built target qpid-proton-core
> [100%] Built target go-pkg-link
> # github.com/apache/qpid-proton/go/pkg/amqp
> go/pkg/amqp/types.go:32:9: cannot define new methods on non-local type
> C.pn_type_t
> go/pkg/amqp/unmarshal.go:729:13: cannot define new methods on non-local type
> *C.pn_data_t
> go/pkg/amqp/unmarshal.go:730:13: cannot define new methods on non-local type
> *C.pn_data_t
> go/pkg/amqp/unmarshal.go:731:13: cannot define new methods on non-local type
> *C.pn_data_t
> make[3]: *** [go/CMakeFiles/go-build.dir/build.make:70:
> go/CMakeFiles/go-build] Error 1
> make[2]: *** [CMakeFiles/Makefile2:1634: go/CMakeFiles/go-build.dir/all]
> Error 2
> make[1]: *** [CMakeFiles/Makefile2:1641: go/CMakeFiles/go-build.dir/rule]
> Error 2
> make: *** [Makefile:842: go-build] Error 2
> [root@tripleo-standalone BLD]# {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2782) golang binding build fails
Martin created PROTON-2782:
--
Summary: golang binding build fails
Key: PROTON-2782
URL: https://issues.apache.org/jira/browse/PROTON-2782
Project: Qpid Proton
Issue Type: Bug
Reporter: Martin
Build of the golang binding fails with Go 1.21 with "cannot define new methods
on non-local type C.pn_type_t".
{code:java}
[root@tripleo-standalone qpid-proton-0.39.0]# cmake -B ./BLD -S $PWD
-- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
-- Could NOT find CyrusSASL (missing: CyrusSASL_LIBRARY CyrusSASL_INCLUDE_DIR)
-- Build type is "RelWithDebInfo" (has debug symbols)
-- PN_VERSION: 0.39.0 ()
-- Building the epoll proactor
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
CMake Warning at c/tests/CMakeLists.txt:142 (message):
No C++ compiler, some C library tests were not built
-- Found Go: /usr/bin/go (go version go1.21.3 linux/amd64) (1.21).
-- Configuring done (0.4s)
-- Generating done (0.0s)
-- Build files have been written to:
/root/golang-qpid-apache/qpid-proton-0.39.0/BLD
[root@tripleo-standalone qpid-proton-0.39.0]# cd BLD/
[root@tripleo-standalone BLD]# make go-build
[ 0%] Built target go-mod-link
[ 9%] Built target generated_c_files
[ 97%] Built target qpid-proton-core-objects
[100%] Built target qpid-proton-core
[100%] Built target go-pkg-link
# github.com/apache/qpid-proton/go/pkg/amqp
go/pkg/amqp/types.go:32:9: cannot define new methods on non-local type
C.pn_type_t
go/pkg/amqp/unmarshal.go:729:13: cannot define new methods on non-local type
*C.pn_data_t
go/pkg/amqp/unmarshal.go:730:13: cannot define new methods on non-local type
*C.pn_data_t
go/pkg/amqp/unmarshal.go:731:13: cannot define new methods on non-local type
*C.pn_data_t
make[3]: *** [go/CMakeFiles/go-build.dir/build.make:70: go/CMakeFiles/go-build]
Error 1
make[2]: *** [CMakeFiles/Makefile2:1634: go/CMakeFiles/go-build.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1641: go/CMakeFiles/go-build.dir/rule] Error
2
make: *** [Makefile:842: go-build] Error 2
[root@tripleo-standalone BLD]# {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8661) [Broker-J] Apache Directory dependencies update
[ https://issues.apache.org/jira/browse/QPID-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8661. -- Resolution: Implemented > [Broker-J] Apache Directory dependencies update > --- > > Key: QPID-8661 > URL: https://issues.apache.org/jira/browse/QPID-8661 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > New version of Apache Directory (2.0.0.AM27) was released, which is used in > broker tests with LDAP. This version removed some kerberos functionality, and > when updating the dependency version refactoring of the affected unit tests > will be needed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8660) Logback logging disabled by inclusion of qpid-broker as a dependency
[
https://issues.apache.org/jira/browse/QPID-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8660:
-
Fix Version/s: qpid-java-broker-9.1.1
> Logback logging disabled by inclusion of qpid-broker as a dependency
>
>
> Key: QPID-8660
> URL: https://issues.apache.org/jira/browse/QPID-8660
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Adrian Pasternak
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> Adding qpid-broker as a project dependency:
> {code:java}
>
> org.apache.qpid
> qpid-broker
> 9.1.0
> {code}
> Disables all logback logging in the application.
>
> This behavior is caused by a change:
> [https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/logging-logback/src/main/java/org/apache/qpid/server/logging/logback/NoopConfigurator.java#L33]
>
> Mailing list discussion:
> [https://lists.apache.org/thread/ms9ddg0kstkdh3yq2ytxtdnlq2dyhps1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8658) [Broker-J] Add Java 21 to the GitHub test matrix
[ https://issues.apache.org/jira/browse/QPID-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8658. -- Resolution: Implemented > [Broker-J] Add Java 21 to the GitHub test matrix > > > Key: QPID-8658 > URL: https://issues.apache.org/jira/browse/QPID-8658 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > To guarantee the compatibility with the future LTS Java version it would be > needed to add Java 21 to the GitHub test matrix along with Java 11 and 17. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8657. -- Resolution: Fixed > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796084#comment-17796084 ] ASF GitHub Bot commented on QPID-8657: -- vavrtom merged PR #229: URL: https://github.com/apache/qpid-broker-j/pull/229 > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796085#comment-17796085 ] ASF subversion and git services commented on QPID-8657: --- Commit 1bc24137d82338a6137c42a97ef13df3bdd1b5d3 in qpid-broker-j's branch refs/heads/main from Daniil Kirilyuk [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=1bc24137d8 ] QPID-8657: [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state (#229) * QPID-8657: [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state * Updated formatting of RuleBasedVirtualHostAccessControlProviderImplTest.java - Co-authored-by: vavrtom > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8656) [Broker-J] Selector parsing logic error when combining NOT and LIKE
[ https://issues.apache.org/jira/browse/QPID-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8656. -- Resolution: Fixed > [Broker-J] Selector parsing logic error when combining NOT and LIKE > --- > > Key: QPID-8656 > URL: https://issues.apache.org/jira/browse/QPID-8656 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > The JMSSelectorFilter.match() gives unexpected results when combining the > LIKE and NOT operators. > The selector "NOT (entry LIKE '%aaa%')" and value "" returns true, as > expected, > The selector "NOT entry LIKE '%aaa%'" and value "" returns false, whcih > is a bug. > In both cases the method retuns true when the value is "" > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [PR] QPID-8657: [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state [qpid-broker-j]
vavrtom merged PR #229: URL: https://github.com/apache/qpid-broker-j/pull/229 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8657: - Fix Version/s: qpid-java-broker-9.1.1 > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8656) [Broker-J] Selector parsing logic error when combining NOT and LIKE
[ https://issues.apache.org/jira/browse/QPID-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796078#comment-17796078 ] ASF subversion and git services commented on QPID-8656: --- Commit 8f7909fbb2d6f9eae22b84e3a4782af6d7d70bbc in qpid-broker-j's branch refs/heads/main from Daniil Kirilyuk [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=8f7909fbb2 ] QPID-8656: [Broker-J] Selector parsing logic error when combining NOT and LIKE (#230) > [Broker-J] Selector parsing logic error when combining NOT and LIKE > --- > > Key: QPID-8656 > URL: https://issues.apache.org/jira/browse/QPID-8656 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > The JMSSelectorFilter.match() gives unexpected results when combining the > LIKE and NOT operators. > The selector "NOT (entry LIKE '%aaa%')" and value "" returns true, as > expected, > The selector "NOT entry LIKE '%aaa%'" and value "" returns false, whcih > is a bug. > In both cases the method retuns true when the value is "" > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8656) [Broker-J] Selector parsing logic error when combining NOT and LIKE
[ https://issues.apache.org/jira/browse/QPID-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796077#comment-17796077 ] ASF GitHub Bot commented on QPID-8656: -- vavrtom merged PR #230: URL: https://github.com/apache/qpid-broker-j/pull/230 > [Broker-J] Selector parsing logic error when combining NOT and LIKE > --- > > Key: QPID-8656 > URL: https://issues.apache.org/jira/browse/QPID-8656 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > The JMSSelectorFilter.match() gives unexpected results when combining the > LIKE and NOT operators. > The selector "NOT (entry LIKE '%aaa%')" and value "" returns true, as > expected, > The selector "NOT entry LIKE '%aaa%'" and value "" returns false, whcih > is a bug. > In both cases the method retuns true when the value is "" > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [PR] QPID-8656: [Broker-J] Selector parsing logic error when combining NOT and LIKE [qpid-broker-j]
vavrtom merged PR #230: URL: https://github.com/apache/qpid-broker-j/pull/230 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
