[jira] [Resolved] (PROTON-2452) Connection Dynamic Receiver create API not applying user configuration in all cases

[ https://issues.apache.org/jira/browse/PROTON-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2452. - Resolution: Fixed > Connection Dynamic Receiver create API not applying user

[jira] [Commented] (PROTON-2452) Connection Dynamic Receiver create API not applying user configuration in all cases

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

[jira] [Created] (PROTON-2452) Connection Dynamic Receiver create API not applying user configuration in all cases

Timothy A. Bish created PROTON-2452: --- Summary: Connection Dynamic Receiver create API not applying user configuration in all cases Key: PROTON-2452 URL: https://issues.apache.org/jira/browse/PROTON-2452

[jira] [Commented] (PROTON-2406) [cpp] Use of reconnect_options::failover_urls triggers -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp

[ https://issues.apache.org/jira/browse/PROTON-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436982#comment-17436982 ] ASF GitHub Bot commented on PROTON-2406: cliffjansen commented on pull request #337: URL:

[GitHub] [qpid-proton] cliffjansen commented on pull request #337: PROTON-2406: [cpp] Replace uses of deprecated reconnect_options::failover_urls with conn…

cliffjansen commented on pull request #337: URL: https://github.com/apache/qpid-proton/pull/337#issuecomment-956502433 As I read the documentation for reconnect_url() and failover_urls() I implicitly expect the same intention for: - default reconnect timing options - change

[jira] [Commented] (DISPATCH-2085) system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event: Assertion `addr->edge_outlink == 0' failed

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

[jira] [Commented] (DISPATCH-2085) system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event: Assertion `addr->edge_outlink == 0' failed

[ https://issues.apache.org/jira/browse/DISPATCH-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436968#comment-17436968 ] ASF GitHub Bot commented on DISPATCH-2085: -- kgiusti merged pull request #1415: URL:

[jira] [Resolved] (DISPATCH-2085) system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event: Assertion `addr->edge_outlink == 0' failed

[ https://issues.apache.org/jira/browse/DISPATCH-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-2085. -- Resolution: Fixed > system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event:

[GitHub] [qpid-dispatch] kgiusti merged pull request #1415: DISPATCH-2085: remove bad assertion in addr_proxy connection handler

kgiusti merged pull request #1415: URL: https://github.com/apache/qpid-dispatch/pull/1415 -- 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:

[jira] [Created] (PROTON-2451) Reduce (ultimately eliminate) all use of the pn_data_t data structure in AMQP frame processing

Andrew Stitcher created PROTON-2451: --- Summary: Reduce (ultimately eliminate) all use of the pn_data_t data structure in AMQP frame processing Key: PROTON-2451 URL:

[jira] [Assigned] (DISPATCH-1966) Update top level Dockerfile to CentOS 8 / CentOS 8 Stream

[ https://issues.apache.org/jira/browse/DISPATCH-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-1966: --- Assignee: Jiri Daněk (was: Ganesh Murthy) > Update top level Dockerfile to

[jira] [Resolved] (DISPATCH-1966) Update top level Dockerfile to CentOS 8 / CentOS 8 Stream

[ https://issues.apache.org/jira/browse/DISPATCH-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1966. - Resolution: Fixed > Update top level Dockerfile to CentOS 8 / CentOS 8 Stream >

[jira] [Resolved] (DISPATCH-2117) Assertion failure outs.count("edge-downlink") != 4 in system_tests_edge_router

[ https://issues.apache.org/jira/browse/DISPATCH-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2117. - Fix Version/s: 1.18.0 Resolution: Fixed This issue might get fixed by the fix

[jira] [Resolved] (DISPATCH-2247) "Received MAU from an unknown router" error message must include unknown router id

[ https://issues.apache.org/jira/browse/DISPATCH-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2247. - Assignee: Ganesh Murthy Resolution: Fixed > "Received MAU from an unknown

[jira] [Commented] (DISPATCH-2247) "Received MAU from an unknown router" error message must include unknown router id

[ https://issues.apache.org/jira/browse/DISPATCH-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436915#comment-17436915 ] ASF GitHub Bot commented on DISPATCH-2247: -- asfgit merged pull request #1414: URL:

[jira] [Commented] (DISPATCH-2247) "Received MAU from an unknown router" error message must include unknown router id

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

[GitHub] [qpid-dispatch] asfgit merged pull request #1414: DISPATCH-2247: Added router id to log message

asfgit merged pull request #1414: URL: https://github.com/apache/qpid-dispatch/pull/1414 -- 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:

[jira] [Reopened] (DISPATCH-2262) Edge/Interior connections can half-fail in real multi-cloud environments

[ https://issues.apache.org/jira/browse/DISPATCH-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened DISPATCH-2262: -- Reopening to note comments on PR. > Edge/Interior connections can half-fail in real

[jira] [Commented] (DISPATCH-2247) "Received MAU from an unknown router" error message must include unknown router id

[ https://issues.apache.org/jira/browse/DISPATCH-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436890#comment-17436890 ] ASF GitHub Bot commented on DISPATCH-2247: -- ted-ross commented on a change in pull request

[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #1414: DISPATCH-2247: Added router id to log message

ted-ross commented on a change in pull request #1414: URL: https://github.com/apache/qpid-dispatch/pull/1414#discussion_r740289989 ## File path: src/router_core/modules/mobile_sync/mobile.c ## @@ -690,8 +690,24 @@ static void qcm_mobile_sync_on_mau_CT(qdrm_mobile_sync_t

[jira] [Commented] (DISPATCH-848) Direct leak of 48 byte(s) in 1 object(s) allocated from qdr_core_subscribe in router_core/route_tables.c:149

[ https://issues.apache.org/jira/browse/DISPATCH-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436888#comment-17436888 ] ASF GitHub Bot commented on DISPATCH-848: - jiridanek commented on pull request #1052: URL:

[jira] [Commented] (DISPATCH-2247) "Received MAU from an unknown router" error message must include unknown router id

[ https://issues.apache.org/jira/browse/DISPATCH-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436889#comment-17436889 ] ASF GitHub Bot commented on DISPATCH-2247: -- ted-ross commented on a change in pull request

[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #1414: DISPATCH-2247: Added router id to log message

ted-ross commented on a change in pull request #1414: URL: https://github.com/apache/qpid-dispatch/pull/1414#discussion_r740289212 ## File path: src/router_core/modules/mobile_sync/mobile.c ## @@ -690,8 +690,24 @@ static void qcm_mobile_sync_on_mau_CT(qdrm_mobile_sync_t

[GitHub] [qpid-dispatch] jiridanek commented on pull request #1052: DISPATCH-848, DISPATCH-1962 Fix leak of IoAdapter_init

jiridanek commented on pull request #1052: URL: https://github.com/apache/qpid-dispatch/pull/1052#issuecomment-956317441 @kgiusti No, there are CI failures (crash somewhere in the depths of Python interpreter). I suspect it could be related to

[jira] [Resolved] (DISPATCH-2223) Incorporate pythoncapi_compat.h to keep up with CPython development

[ https://issues.apache.org/jira/browse/DISPATCH-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk resolved DISPATCH-2223. -- Resolution: Fixed > Incorporate pythoncapi_compat.h to keep up with CPython development >

[jira] [Commented] (DISPATCH-2085) system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event: Assertion `addr->edge_outlink == 0' failed

[ https://issues.apache.org/jira/browse/DISPATCH-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436881#comment-17436881 ] Ken Giusti commented on DISPATCH-2085: -- Turns out that assert is now invalid due to the addition

[jira] [Commented] (DISPATCH-2234) Update JavaScript console packages for the 1.18.0 release

[ https://issues.apache.org/jira/browse/DISPATCH-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436876#comment-17436876 ] Jiri Daněk commented on DISPATCH-2234: -- Hmm, should I do this, or leave it for next release

[jira] [Resolved] (DISPATCH-840) "schema.adoc" contains invalid asciidoc

[ https://issues.apache.org/jira/browse/DISPATCH-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk resolved DISPATCH-840. - Resolution: Fixed > "schema.adoc" contains invalid asciidoc >

[jira] [Updated] (DISPATCH-836) Source file organization suffers from include hell

[ https://issues.apache.org/jira/browse/DISPATCH-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-836: Fix Version/s: (was: 1.18.0) 1.19.0 > Source file organization suffers

[jira] [Resolved] (DISPATCH-2121) Investigate whether there might be benefits from LTO-ing Proton into Dispatch

[ https://issues.apache.org/jira/browse/DISPATCH-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk resolved DISPATCH-2121. -- Resolution: Later There may be benefits and it is now possible to link static build of

[jira] [Commented] (DISPATCH-2143) race getting/setting qdr_delivery_t->disposition

[ https://issues.apache.org/jira/browse/DISPATCH-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436867#comment-17436867 ] Jiri Daněk commented on DISPATCH-2143: --

[jira] [Resolved] (DISPATCH-2193) system_tests_http1_over_tcp failing in test_05_large_streaming_msg

[ https://issues.apache.org/jira/browse/DISPATCH-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2193. - Fix Version/s: 1.18.0 Resolution: Cannot Reproduce >

[jira] [Updated] (DISPATCH-2273) Remove support for Proton < 0.33 SASL extension API

[ https://issues.apache.org/jira/browse/DISPATCH-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-2273: - Fix Version/s: 1.18.0 > Remove support for Proton < 0.33 SASL extension API >

[jira] [Resolved] (DISPATCH-2273) Remove support for Proton < 0.33 SASL extension API

[ https://issues.apache.org/jira/browse/DISPATCH-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk resolved DISPATCH-2273. -- Resolution: Fixed > Remove support for Proton < 0.33 SASL extension API >

[jira] [Assigned] (DISPATCH-2273) Remove support for Proton < 0.33 SASL extension API

[ https://issues.apache.org/jira/browse/DISPATCH-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk reassigned DISPATCH-2273: Assignee: Jiri Daněk > Remove support for Proton < 0.33 SASL extension API >

[jira] [Commented] (DISPATCH-2273) Remove support for Proton < 0.33 SASL extension API

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

[jira] [Commented] (DISPATCH-2273) Remove support for Proton < 0.33 SASL extension API

[ https://issues.apache.org/jira/browse/DISPATCH-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436856#comment-17436856 ] ASF GitHub Bot commented on DISPATCH-2273: -- jiridanek merged pull request #1411: URL:

[GitHub] [qpid-dispatch] jiridanek merged pull request #1411: DISPATCH-2273 Remove compatibility for pre-PROTON-2257 SASL Extension API needed for Proton < 0.33

jiridanek merged pull request #1411: URL: https://github.com/apache/qpid-dispatch/pull/1411 -- 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:

[jira] [Resolved] (DISPATCH-2269) warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef]

[ https://issues.apache.org/jira/browse/DISPATCH-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk resolved DISPATCH-2269. -- Resolution: Fixed > warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef] >

[jira] [Updated] (DISPATCH-2269) warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef]

[ https://issues.apache.org/jira/browse/DISPATCH-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-2269: - Status: Reviewable (was: In Progress) > warning: 'PN_VERSON_MINOR' is not defined, evaluates

[jira] [Assigned] (DISPATCH-2269) warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef]

[ https://issues.apache.org/jira/browse/DISPATCH-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk reassigned DISPATCH-2269: Assignee: Jiri Daněk > warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0

[jira] [Commented] (DISPATCH-2269) warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef]

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

[jira] [Commented] (DISPATCH-2269) warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef]

[ https://issues.apache.org/jira/browse/DISPATCH-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436854#comment-17436854 ] ASF GitHub Bot commented on DISPATCH-2269: -- jiridanek merged pull request #1410: URL:

[jira] [Updated] (DISPATCH-2269) warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef]

[ https://issues.apache.org/jira/browse/DISPATCH-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-2269: - Fix Version/s: 1.18.0 > warning: 'PN_VERSON_MINOR' is not defined, evaluates to 0 [-Wundef] >

[GitHub] [qpid-dispatch] jiridanek merged pull request #1410: DISPATCH-2269 Remove PROTON-2184 session context workaround needed for Proton < 0.31

jiridanek merged pull request #1410: URL: https://github.com/apache/qpid-dispatch/pull/1410 -- 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:

[jira] [Resolved] (DISPATCH-2224) system_tests_policy_oversize_compound: router_node.c:452: AMQP_rx_handler: Assertion `pn_link' failed

[ https://issues.apache.org/jira/browse/DISPATCH-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2224. - Fix Version/s: 1.18.0 Resolution: Cannot Reproduce I tried running this test

[jira] [Commented] (QPID-8565) [Broker-J] Enhancement of ACL rule predicates evaluation

[ https://issues.apache.org/jira/browse/QPID-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436840#comment-17436840 ] ASF GitHub Bot commented on QPID-8565: -- alex-rufous commented on a change in pull request #113: URL:

[GitHub] [qpid-broker-j] alex-rufous commented on a change in pull request #113: QPID-8565: [Broker-J] Enhancement of ACL rule predicates evaluation

alex-rufous commented on a change in pull request #113: URL: https://github.com/apache/qpid-broker-j/pull/113#discussion_r740213872 ## File path: broker-plugins/access-control/src/main/java/org/apache/qpid/server/security/access/config/RulePredicate.java ## @@ -62,5 +71,16 @@

[GitHub] [qpid-broker-j] alex-rufous commented on a change in pull request #113: QPID-8565: [Broker-J] Enhancement of ACL rule predicates evaluation

alex-rufous commented on a change in pull request #113: URL: https://github.com/apache/qpid-broker-j/pull/113#discussion_r740212386 ## File path: broker-plugins/access-control/src/main/java/org/apache/qpid/server/security/access/config/AclRulePredicatesBuilder.java ## @@

[jira] [Commented] (QPID-8565) [Broker-J] Enhancement of ACL rule predicates evaluation

[ https://issues.apache.org/jira/browse/QPID-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436836#comment-17436836 ] ASF GitHub Bot commented on QPID-8565: -- alex-rufous commented on a change in pull request #113: URL:

[jira] [Commented] (QPID-8565) [Broker-J] Enhancement of ACL rule predicates evaluation

[ https://issues.apache.org/jira/browse/QPID-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436829#comment-17436829 ] ASF GitHub Bot commented on QPID-8565: -- alex-rufous commented on pull request #113: URL:

[GitHub] [qpid-broker-j] alex-rufous commented on pull request #113: QPID-8565: [Broker-J] Enhancement of ACL rule predicates evaluation

alex-rufous commented on pull request #113: URL: https://github.com/apache/qpid-broker-j/pull/113#issuecomment-956234276 > CONNECTION_LIMIT and CONNECTION_FREQUENCY_LIMIT properties are deprecated and they are not supported. That is not a precise statement. The support for

[jira] [Resolved] (DISPATCH-2109) Shutdown crash: member access within null pointer of type 'struct qdr_node_t'

[ https://issues.apache.org/jira/browse/DISPATCH-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2109. - Resolution: Fixed > Shutdown crash: member access within null pointer of type 'struct

[jira] [Commented] (DISPATCH-2109) Shutdown crash: member access within null pointer of type 'struct qdr_node_t'

[ https://issues.apache.org/jira/browse/DISPATCH-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436815#comment-17436815 ] Ganesh Murthy commented on DISPATCH-2109: - I am going to assume that the fix for DISPATCH-2230

[jira] [Resolved] (DISPATCH-2268) HTTP/1.x: incorrectly logs connection close as an error

[ https://issues.apache.org/jira/browse/DISPATCH-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-2268. -- Resolution: Fixed > HTTP/1.x: incorrectly logs connection close as an error >

[jira] [Commented] (DISPATCH-2268) HTTP/1.x: incorrectly logs connection close as an error

[ https://issues.apache.org/jira/browse/DISPATCH-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436810#comment-17436810 ] ASF GitHub Bot commented on DISPATCH-2268: -- kgiusti commented on pull request #1408: URL:

[jira] [Commented] (DISPATCH-2268) HTTP/1.x: incorrectly logs connection close as an error

[ https://issues.apache.org/jira/browse/DISPATCH-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436811#comment-17436811 ] ASF GitHub Bot commented on DISPATCH-2268: -- kgiusti closed pull request #1408: URL:

[GitHub] [qpid-dispatch] kgiusti closed pull request #1408: DISPATCH-2268: fix misleading log messages in the HTTP/1.x adaptor

kgiusti closed pull request #1408: URL: https://github.com/apache/qpid-dispatch/pull/1408 -- 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:

[GitHub] [qpid-dispatch] kgiusti commented on pull request #1408: DISPATCH-2268: fix misleading log messages in the HTTP/1.x adaptor

kgiusti commented on pull request #1408: URL: https://github.com/apache/qpid-dispatch/pull/1408#issuecomment-956204998 Merged https://github.com/apache/qpid-dispatch/commit/72034876c94aee730ef5b1556f1c86c9685103f1 -- This is an automated message from the Apache Git Service. To respond

[jira] [Commented] (DISPATCH-2268) HTTP/1.x: incorrectly logs connection close as an error

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

[jira] [Commented] (PROTON-2400) 0.36.0 release tasks

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

[jira] [Commented] (PROTON-2400) 0.36.0 release tasks

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

[jira] [Commented] (PROTON-2442) 0.37.0 release tasks

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

[jira] [Updated] (DISPATCH-2274) system_tests_router_mesh: ERROR: AddressSanitizer: use-after-poison in qd_link_pn container.c:1029

[ https://issues.apache.org/jira/browse/DISPATCH-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-2274: - Environment: Aarch64 Linux, amd64 macOS (was: macOS) > system_tests_router_mesh: ERROR:

[jira] [Commented] (DISPATCH-2114) Leak of qdr_link_t and qdr_terminus_t in system_tests_policy

[ https://issues.apache.org/jira/browse/DISPATCH-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436785#comment-17436785 ] Jiri Daněk commented on DISPATCH-2114: -- I saw it again on Aarch64

[jira] [Commented] (DISPATCH-2245) [TSan] data race in qdr_link_process_deliveries during system_tests_delivery_counts

[ https://issues.apache.org/jira/browse/DISPATCH-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436784#comment-17436784 ] Jiri Daněk commented on DISPATCH-2245: --

[jira] [Commented] (PROTON-2400) 0.36.0 release tasks

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

[jira] [Commented] (DISPATCH-2109) Shutdown crash: member access within null pointer of type 'struct qdr_node_t'

[ https://issues.apache.org/jira/browse/DISPATCH-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436782#comment-17436782 ] Jiri Daněk commented on DISPATCH-2109: -- This issue has not reappeared in a few recent builds on

[jira] [Commented] (DISPATCH-2197) Data race in system_tests_auth_service_plugin involving remote_sasl_list_mechs

[ https://issues.apache.org/jira/browse/DISPATCH-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436776#comment-17436776 ] Jiri Daněk commented on DISPATCH-2197: --

[jira] [Commented] (DISPATCH-2274) system_tests_router_mesh: ERROR: AddressSanitizer: use-after-poison in qd_link_pn container.c:1029

[ https://issues.apache.org/jira/browse/DISPATCH-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436770#comment-17436770 ] Jiri Daněk commented on DISPATCH-2274: -- Again, this time on Arm, with a different stacktrace

[jira] [Commented] (PROTON-2441) [cpp] Crash upon reconnect when user passed empty vector to connection_options::failover_urls

[ https://issues.apache.org/jira/browse/PROTON-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436761#comment-17436761 ] ASF GitHub Bot commented on PROTON-2441: gemmellr commented on pull request #338: URL:

[GitHub] [qpid-proton] gemmellr commented on pull request #338: PROTON-2441: [cpp] Fix connection_options failover urls segfault

gemmellr commented on pull request #338: URL: https://github.com/apache/qpid-proton/pull/338#issuecomment-956139968 The change itself seems reasonable to me, it looks similar to what the other bit a little above it is doing. I know Jiri thought, and I agree, that ensuring a test of

[jira] [Updated] (PROTON-2441) [cpp] Crash upon reconnect when user passed empty vector to connection_options::failover_urls

[ https://issues.apache.org/jira/browse/PROTON-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2441: --- Fix Version/s: proton-c-0.37.0 Affects Version/s: proton-c-0.36.0 > [cpp] Crash

[jira] [Updated] (PROTON-2406) [cpp] Use of reconnect_options::failover_urls triggers -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp

[ https://issues.apache.org/jira/browse/PROTON-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2406: --- Affects Version/s: (was: proton-c-0.35.0) proton-c-0.36.0 >

[jira] [Updated] (PROTON-2406) [cpp] Use of reconnect_options::failover_urls triggers -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp

[ https://issues.apache.org/jira/browse/PROTON-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2406: --- Fix Version/s: proton-c-0.37.0 > [cpp] Use of reconnect_options::failover_urls triggers >

[jira] [Commented] (PROTON-2254) Relative paths in CMake share

[ https://issues.apache.org/jira/browse/PROTON-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436736#comment-17436736 ] ASF GitHub Bot commented on PROTON-2254: gemmellr commented on pull request #335: URL:

[GitHub] [qpid-proton] gemmellr commented on pull request #335: PROTON-2254 Generate correct relocatable pc files

gemmellr commented on pull request #335: URL: https://github.com/apache/qpid-proton/pull/335#issuecomment-956115988 Raised https://issues.apache.org/jira/browse/PROTON-2450 to retarget this PR against for future release. -- This is an automated message from the Apache Git Service. To

[jira] [Updated] (PROTON-2450) Generate correct relocatable pc files

[ https://issues.apache.org/jira/browse/PROTON-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2450: --- Description: Offshoot from PROTON-2254 / PROTON-2433 for continuing with

[jira] [Commented] (PROTON-2254) Relative paths in CMake share

[ https://issues.apache.org/jira/browse/PROTON-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436735#comment-17436735 ] Robbie Gemmell commented on PROTON-2254: Raised PROTON-2450 for continuing with

[jira] [Created] (PROTON-2450) Generate correct relocatable pc files

Robbie Gemmell created PROTON-2450: -- Summary: Generate correct relocatable pc files Key: PROTON-2450 URL: https://issues.apache.org/jira/browse/PROTON-2450 Project: Qpid Proton Issue Type:

[jira] [Updated] (PROTON-1647) [go] support for crypto.tls connections

[ https://issues.apache.org/jira/browse/PROTON-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1647: Fix Version/s: proton-c-future > [go] support for crypto.tls connections >

[jira] [Commented] (QPID-8565) [Broker-J] Enhancement of ACL rule predicates evaluation

[ https://issues.apache.org/jira/browse/QPID-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436732#comment-17436732 ] ASF GitHub Bot commented on QPID-8565: -- mklaca opened a new pull request #113: URL:

[GitHub] [qpid-broker-j] mklaca opened a new pull request #113: QPID-8565: [Broker-J] Enhancement of ACL rule predicates evaluation

mklaca opened a new pull request #113: URL: https://github.com/apache/qpid-broker-j/pull/113 CONNECTION_LIMIT and CONNECTION_FREQUENCY_LIMIT properties are deprecated and they are not supported. Actual implementation silently parse and add a new predicate. This is the worst scenario

[jira] [Updated] (PROTON-2376) container.listen may support amqps

[ https://issues.apache.org/jira/browse/PROTON-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2376: Labels: tls (was: ) > container.listen may support amqps > -- >

[jira] [Updated] (PROTON-2122) Hardcoded limit of 16 sasl mechanisms is insufficient on macOS

[ https://issues.apache.org/jira/browse/PROTON-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2122: Labels: sasl (was: ) > Hardcoded limit of 16 sasl mechanisms is insufficient on macOS >

[jira] [Updated] (PROTON-2434) Container.connect doesn't set virtual_host by default, making peer verification harder than it should be

[ https://issues.apache.org/jira/browse/PROTON-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2434: Labels: tls (was: ) > Container.connect doesn't set virtual_host by default, making peer >

[jira] [Updated] (PROTON-1057) Windows SChannel SSL test failure

[ https://issues.apache.org/jira/browse/PROTON-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1057: Labels: tls windows (was: windows) > Windows SChannel SSL test failure >

[jira] [Updated] (PROTON-1802) Support compiling with -DSSL_IMPL=openssl on Windows

[ https://issues.apache.org/jira/browse/PROTON-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1802: Labels: tls (was: ) > Support compiling with -DSSL_IMPL=openssl on Windows >

[jira] [Updated] (PROTON-2009) OpenSSL API has changed and now deprecates SSL_OP_NO_TLSv* used with SSL_CTX_set_options

[ https://issues.apache.org/jira/browse/PROTON-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2009: Labels: tls (was: ) > OpenSSL API has changed and now deprecates SSL_OP_NO_TLSv* used with >

[jira] [Updated] (PROTON-1864) [c] No way of indicating that a transport is ssl or encrypted or already authenticated

[ https://issues.apache.org/jira/browse/PROTON-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1864: Labels: tls (was: ) > [c] No way of indicating that a transport is ssl or encrypted or already

[jira] [Updated] (PROTON-855) Add axTLS (embedded SSL) support to proton-c

[ https://issues.apache.org/jira/browse/PROTON-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-855: --- Labels: features patch tls (was: features patch) > Add axTLS (embedded SSL) support to proton-c >

[jira] [Updated] (PROTON-1870) better logging for ssl

[ https://issues.apache.org/jira/browse/PROTON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1870: Labels: logging tls usability (was: logging usability) > better logging for ssl >

[jira] [Updated] (PROTON-2303) SSL Unknown Error

[ https://issues.apache.org/jira/browse/PROTON-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2303: Labels: tls (was: ) > SSL Unknown Error > - > > Key: PROTON-2303

[jira] [Commented] (PROTON-2441) [cpp] Crash upon reconnect when user passed empty vector to connection_options::failover_urls

[ https://issues.apache.org/jira/browse/PROTON-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436672#comment-17436672 ] ASF GitHub Bot commented on PROTON-2441: DreamPearl commented on pull request #338: URL:

[GitHub] [qpid-proton] DreamPearl commented on pull request #338: PROTON-2441: [cpp] Fix connection_options failover urls segfault

DreamPearl commented on pull request #338: URL: https://github.com/apache/qpid-proton/pull/338#issuecomment-956023315 @gemmellr @jiridanek Can you please take a look. The cause of segfault was that when we were passing empty vector to connection_options::failoverurls, the current_url