[jira] [Resolved] (PROTON-2673) Proactor hangs if pn_raw_connection_wake() is called with outstanding connection attempt
[
https://issues.apache.org/jira/browse/PROTON-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clifford Jansen resolved PROTON-2673.
-
Fix Version/s: proton-c-0.39.0
Resolution: Fixed
> Proactor hangs if pn_raw_connection_wake() is called with outstanding
> connection attempt
>
>
> Key: PROTON-2673
> URL: https://issues.apache.org/jira/browse/PROTON-2673
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.38.0, proton-c-0.39.0
>Reporter: Ken Giusti
>Assignee: Clifford Jansen
>Priority: Major
> Fix For: proton-c-0.39.0
>
> Attachments: raw_wake.c
>
>
> If pn_raw_connection_wake() is called on a raw connection that is attempting
> to connect no further proactor events are generated and the proactor hangs.
> Important observations:
> * This only occurs {_}if there is no server available at the target address
> for the connection{_}. If a server is present then the PN_RAW_CONNECTION_WAKE
> and PN_RAW_CONNECTION_CONNECTED events arrive properly (in that order).
> * The host address is "localhost" - using "127.0.0.1" or "::1" instead
> works. localhost on my machine maps to both "127.0.0.1" and "::1"
> * Extra bonus: if you move the call to pn_raw_connection_wake() to _before_
> the call to pn_proactor_raw_connect() a crash occurs
> See attached reproducer.
--
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] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2401. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.39.0 > > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- 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] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711125#comment-17711125 ] ASF subversion and git services commented on PROTON-2401: - Commit 0847d3aed940714c4da57353ccf753a88e456983 in qpid-proton's branch refs/heads/main from Sebastiaan la Fleur [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=0847d3aed ] PROTON-2401: [Python] on_xxx_closed should be called on locally closed after remote close When links/sessions/connections are remotely closed then locally closed the on_xxx_closed event should still fire. The existing code only fires this event for local then remote close. > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- 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] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711127#comment-17711127 ] ASF GitHub Bot commented on PROTON-2401: asfgit merged PR #391: URL: https://github.com/apache/qpid-proton/pull/391 > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- 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
[GitHub] [qpid-proton] asfgit merged pull request #391: PROTON-2401: [Python] on_xxx_closed should be called on locally closed after remote close
asfgit merged PR #391: URL: https://github.com/apache/qpid-proton/pull/391 -- 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] [Resolved] (PROTON-2679) Parallel build of python bindings occasionally fails
[ https://issues.apache.org/jira/browse/PROTON-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2679. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > Parallel build of python bindings occasionally fails > > > Key: PROTON-2679 > URL: https://issues.apache.org/jira/browse/PROTON-2679 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Ken Giusti >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > See skupper CI failure: > [https://github.com/skupperproject/skupper-router/actions/runs/4056555498/jobs/6981190135#step:17:234] > Appears to be trying to build the same file twice: > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_condition.py > proton/_condition.py > > [ 38%] Generating proton/_condition.py > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_condition.py > proton/_condition.py > > [ 39%] Generating proton/_data.py > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_data.py > proton/_data.py > > [ 40%] Generating proton/_data.py > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_data.py > proton/_data.py > > Error copying file > "/home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_condition.py" > to "proton/_condition.py". > > gmake[2]: *** [python/CMakeFiles/pydist.dir/build.make:280: > python/proton/_condition.py] Error 1 > > gmake[2]: *** Deleting file 'python/proton/_condition.py' > > gmake[2]: *** Waiting for unfinished jobs > > gmake[1]: *** [CMakeFiles/Makefile2:572: python/CMakeFiles/pydist.dir/all] > Error 2 > > gmake[2]: Leaving directory > '/__w/skupper-router/skupper-router/qpid-proton/build' > > gmake[1]: *** Waiting for unfinished jobs -- 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] (PROTON-2709) Settle delivered messages in the C sender example
[ https://issues.apache.org/jira/browse/PROTON-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2709. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > Settle delivered messages in the C sender example > - > > Key: PROTON-2709 > URL: https://issues.apache.org/jira/browse/PROTON-2709 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Although it's not needed in the example because the link is fairly short > lived and so doesn't create excessive memory use, the sender should settle > the delivery when the message is accepted so as to free all memory resources > associated with it. This is necessary for a long lived sender and so the > example should show this. -- 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] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711123#comment-17711123 ] ASF GitHub Bot commented on PROTON-2401: astitcher commented on PR #391: URL: https://github.com/apache/qpid-proton/pull/391#issuecomment-1504107879 I've added a test for the connection closed event. > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- 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
[GitHub] [qpid-proton] astitcher commented on pull request #391: PROTON-2401: [Python] on_xxx_closed should be called on locally closed after remote close
astitcher commented on PR #391: URL: https://github.com/apache/qpid-proton/pull/391#issuecomment-1504107879 I've added a test for the connection closed event. -- 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] [Commented] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711084#comment-17711084 ] ASF GitHub Bot commented on PROTON-2401: astitcher commented on PR #323: URL: https://github.com/apache/qpid-proton/pull/323#issuecomment-1503916992 Closed in favor of #391 > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- 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] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711085#comment-17711085 ] ASF GitHub Bot commented on PROTON-2401: astitcher closed pull request #323: PROTON-2401: on_link_closed should be closed when the link is remotel… URL: https://github.com/apache/qpid-proton/pull/323 > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- 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
[GitHub] [qpid-proton] astitcher closed pull request #323: PROTON-2401: on_link_closed should be closed when the link is remotel…
astitcher closed pull request #323: PROTON-2401: on_link_closed should be closed when the link is remotel… URL: https://github.com/apache/qpid-proton/pull/323 -- 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
[GitHub] [qpid-proton] astitcher commented on pull request #323: PROTON-2401: on_link_closed should be closed when the link is remotel…
astitcher commented on PR #323: URL: https://github.com/apache/qpid-proton/pull/323#issuecomment-1503916992 Closed in favor of #391 -- 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] [Commented] (PROTON-2402) Clarify proton python documentation on thread-safety and when certain callbacks are called
[ https://issues.apache.org/jira/browse/PROTON-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711083#comment-17711083 ] ASF GitHub Bot commented on PROTON-2402: astitcher commented on PR #324: URL: https://github.com/apache/qpid-proton/pull/324#issuecomment-1503913800 @ssorj Could you look at these doc changes and see if you think this is an improvement. > Clarify proton python documentation on thread-safety and when certain > callbacks are called > -- > > Key: PROTON-2402 > URL: https://issues.apache.org/jira/browse/PROTON-2402 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Priority: Minor > > The Python documentation does not state the following explicitely which > caused some confusion on my end: > - on_settled is triggered on the disposition settled on remote side > - Container & other proton datastructures are NOT thread safe, use injector > for external thread communication > - on_sendable is called on each received flow event & after send if there > are still credits available. > > PR: https://github.com/apache/qpid-proton/pull/324 -- 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
[GitHub] [qpid-proton] astitcher commented on pull request #324: PROTON-2402: Clarify proton docs for on_sendable, prefetch for Messag…
astitcher commented on PR #324: URL: https://github.com/apache/qpid-proton/pull/324#issuecomment-1503913800 @ssorj Could you look at these doc changes and see if you think this is an improvement. -- 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
[GitHub] [qpid-proton] astitcher commented on pull request #392: Fixing a leak problem.
astitcher commented on PR #392: URL: https://github.com/apache/qpid-proton/pull/392#issuecomment-1503903450 Merged -- 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
[GitHub] [qpid-proton] astitcher closed pull request #392: Fixing a leak problem.
astitcher closed pull request #392: Fixing a leak problem. URL: https://github.com/apache/qpid-proton/pull/392 -- 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] [Commented] (PROTON-2709) Settle delivered messages in the C sender example
[ https://issues.apache.org/jira/browse/PROTON-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17711081#comment-17711081 ] ASF subversion and git services commented on PROTON-2709: - Commit 703b7b8f2b04f6e1196992787bdd113aa4862a6a in qpid-proton's branch refs/heads/main from Danis Ozdemir [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=703b7b8f2 ] PROTON-2709: [C examples] Settle deliveries in sender example If the delivery object is not settled on the sender side, the delivery object does not get returned to the pool of the link. Without the proposed fix, this code will mislead people and the code written based on this example will cause memory exhaustion in the long run. > Settle delivered messages in the C sender example > - > > Key: PROTON-2709 > URL: https://issues.apache.org/jira/browse/PROTON-2709 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > Although it's not needed in the example because the link is fairly short > lived and so doesn't create excessive memory use, the sender should settle > the delivery when the message is accepted so as to free all memory resources > associated with it. This is necessary for a long lived sender and so the > example should show this. -- 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-2709) Settle delivered messages in the C sender example
Andrew Stitcher created PROTON-2709: --- Summary: Settle delivered messages in the C sender example Key: PROTON-2709 URL: https://issues.apache.org/jira/browse/PROTON-2709 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher Although it's not needed in the example because the link is fairly short lived and so doesn't create excessive memory use, the sender should settle the delivery when the message is accepted so as to free all memory resources associated with it. This is necessary for a long lived sender and so the example should show this. -- 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] (PROTON-2095) Move away from SWIG to CFFI
[ https://issues.apache.org/jira/browse/PROTON-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2095: --- Issue Type: Improvement (was: Wish) > Move away from SWIG to CFFI > --- > > Key: PROTON-2095 > URL: https://issues.apache.org/jira/browse/PROTON-2095 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.29.0, proton-c-future >Reporter: Omer Katz >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > SWIG is fine but we're not using it for anything other than exporting all of > proton-c's API as is. > Unfortunately SWIG only generates CPython extension bindings. This may be a > problem on PyPy where CPython extensions are either slow or simply won't > compile. > Unlike SWIG, CFFI is portable both on CPython and PyPy. > It also satisfies the same requirements as SWIG currently does. > In addition, calls to CFFI simply release the GIL which will help > parallelizing Python applications using threads. > By using CFFI we can also get rid of all of our setup.py code and simply use > it to build the extension. We will also no longer have problems building > wheels. > The newest version of CFFI supports pkg-config so we can use that to find > proton-c easily. > I'm willing to help with the refactor but I'll need a mentor since I'm not > familiar with the code base. > -- 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] (PROTON-2708) New proactor APIs to query event batch for subject
[
https://issues.apache.org/jira/browse/PROTON-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved PROTON-2708.
Resolution: Fixed
> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> The object that a proactor event batch refers can't change during the
> processing of the batch so you shouldn't need to extract the object from
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}},
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}
--
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] (PROTON-2708) New proactor APIs to query event batch for subject
[
https://issues.apache.org/jira/browse/PROTON-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-2708:
---
Fix Version/s: proton-c-0.39.0
> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
> Fix For: proton-c-0.39.0
>
>
> The object that a proactor event batch refers can't change during the
> processing of the batch so you shouldn't need to extract the object from
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}},
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}
--
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] (PROTON-2706) [Python] Allow setting the container id for containers/connections
[ https://issues.apache.org/jira/browse/PROTON-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2706. Resolution: Fixed > [Python] Allow setting the container id for containers/connections > -- > > Key: PROTON-2706 > URL: https://issues.apache.org/jira/browse/PROTON-2706 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > This is an improvement suggested by [~jmennius] -- 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] (PROTON-2706) [Python] Allow setting the container id for containers/connections
[ https://issues.apache.org/jira/browse/PROTON-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2706: --- Fix Version/s: proton-c-0.39.0 > [Python] Allow setting the container id for containers/connections > -- > > Key: PROTON-2706 > URL: https://issues.apache.org/jira/browse/PROTON-2706 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > This is an improvement suggested by [~jmennius] -- 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] (PROTON-2677) cpp-example-container test failure
[ https://issues.apache.org/jira/browse/PROTON-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2677. Resolution: Fixed > cpp-example-container test failure > -- > > Key: PROTON-2677 > URL: https://issues.apache.org/jira/browse/PROTON-2677 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Since the commit for PROTON-2657 there have been test failures due to the C++ > broker example crashing and failing the TSAN test runs. -- 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] (PROTON-2677) cpp-example-container test failure
[ https://issues.apache.org/jira/browse/PROTON-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2677: --- Fix Version/s: proton-c-0.39.0 > cpp-example-container test failure > -- > > Key: PROTON-2677 > URL: https://issues.apache.org/jira/browse/PROTON-2677 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Since the commit for PROTON-2657 there have been test failures due to the C++ > broker example crashing and failing the TSAN test runs. -- 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] (PROTON-2669) Change version of cmake supported to 3.16 and up
[ https://issues.apache.org/jira/browse/PROTON-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2669. Resolution: Fixed > Change version of cmake supported to 3.16 and up > > > Key: PROTON-2669 > URL: https://issues.apache.org/jira/browse/PROTON-2669 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > We've supported CMake 2.8.12 for a very long time, but it has made our life > much harder for building. > At this point the orld has moved on and every system we care about has a > newer version of cmake available - 3.16 seems like a fairly conservative > choice (Currently cmake is version 3.25) -- 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] (PROTON-2669) Change version of cmake supported to 3.16 and up
[ https://issues.apache.org/jira/browse/PROTON-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2669: --- Fix Version/s: proton-c-0.39.0 > Change version of cmake supported to 3.16 and up > > > Key: PROTON-2669 > URL: https://issues.apache.org/jira/browse/PROTON-2669 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > We've supported CMake 2.8.12 for a very long time, but it has made our life > much harder for building. > At this point the orld has moved on and every system we care about has a > newer version of cmake available - 3.16 seems like a fairly conservative > choice (Currently cmake is version 3.25) -- 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] (PROTON-2690) [Python] The desired and offered capabilities field in open performative should be symbol array or symbol
[ https://issues.apache.org/jira/browse/PROTON-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2690. Resolution: Fixed > [Python] The desired and offered capabilities field in open performative > should be symbol array or symbol > - > > Key: PROTON-2690 > URL: https://issues.apache.org/jira/browse/PROTON-2690 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Currently if you pass a list (or a symbol list) to connection.open the > performative that goes on the wire contains a list. The AMQP standard > requires that the wire contains a symbol array or a single symbol. -- 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] (PROTON-2690) [Python] The desired and offered capabilities field in open performative should be symbol array or symbol
[ https://issues.apache.org/jira/browse/PROTON-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2690: --- Fix Version/s: proton-c-0.39.0 > [Python] The desired and offered capabilities field in open performative > should be symbol array or symbol > - > > Key: PROTON-2690 > URL: https://issues.apache.org/jira/browse/PROTON-2690 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Currently if you pass a list (or a symbol list) to connection.open the > performative that goes on the wire contains a list. The AMQP standard > requires that the wire contains a symbol array or a single symbol. -- 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] (PROTON-2667) Various CI python test failures
[ https://issues.apache.org/jira/browse/PROTON-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2667. Resolution: Fixed > Various CI python test failures > --- > > Key: PROTON-2667 > URL: https://issues.apache.org/jira/browse/PROTON-2667 > Project: Qpid Proton > Issue Type: Bug >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Various of the python tests have been failing on some or all of the CI builds > for a while. These have a few causes and symptoms. but are all related to > using newer versions of python or the various python modules used in testing. -- 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] (PROTON-2667) Various CI python test failures
[ https://issues.apache.org/jira/browse/PROTON-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2667: --- Fix Version/s: proton-c-0.39.0 > Various CI python test failures > --- > > Key: PROTON-2667 > URL: https://issues.apache.org/jira/browse/PROTON-2667 > Project: Qpid Proton > Issue Type: Bug >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Various of the python tests have been failing on some or all of the CI builds > for a while. These have a few causes and symptoms. but are all related to > using newer versions of python or the various python modules used in testing. -- 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] (PROTON-2708) New proactor APIs to query event batch for subject
[
https://issues.apache.org/jira/browse/PROTON-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710999#comment-17710999
]
ASF GitHub Bot commented on PROTON-2708:
asfgit merged PR #393:
URL: https://github.com/apache/qpid-proton/pull/393
> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
>
> The object that a proactor event batch refers can't change during the
> processing of the batch so you shouldn't need to extract the object from
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}},
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}
--
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] (PROTON-2708) New proactor APIs to query event batch for subject
[
https://issues.apache.org/jira/browse/PROTON-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710998#comment-17710998
]
ASF subversion and git services commented on PROTON-2708:
-
Commit 398dadd6606d25685cd6c6f35d66c9fa2251a651 in qpid-proton's branch
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=398dadd66 ]
PROTON-2708: Introduce new proactor APIs that query batch
These new APIs are useful for querying the proactor event batch for the
object that is the subject of the batch. The proactor guarantees that
the subject of the batch is never returned in any other batch until this
batch is completed.
> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
>
> The object that a proactor event batch refers can't change during the
> processing of the batch so you shouldn't need to extract the object from
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}},
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}
--
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] (PROTON-2666) [C++] Allow more python examples to run using the C++ broker example
[ https://issues.apache.org/jira/browse/PROTON-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2666. Resolution: Fixed > [C++] Allow more python examples to run using the C++ broker example > > > Key: PROTON-2666 > URL: https://issues.apache.org/jira/browse/PROTON-2666 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > It would be nice to be able to run all the in tree examples with an broker > that is in the proton source tree itself. Currently there seem to be 3 > capabilities needed for this: > * Anonymous relay > * Transactions > * Selector filters > Anonymous relay is a fairly simple thing to implement; transactions would be > the next simplest; selectors are somewhat complex and would need to parse an > entire language. -- 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] (PROTON-2666) [C++] Allow more python examples to run using the C++ broker example
[ https://issues.apache.org/jira/browse/PROTON-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2666: --- Fix Version/s: proton-c-0.39.0 > [C++] Allow more python examples to run using the C++ broker example > > > Key: PROTON-2666 > URL: https://issues.apache.org/jira/browse/PROTON-2666 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > It would be nice to be able to run all the in tree examples with an broker > that is in the proton source tree itself. Currently there seem to be 3 > capabilities needed for this: > * Anonymous relay > * Transactions > * Selector filters > Anonymous relay is a fairly simple thing to implement; transactions would be > the next simplest; selectors are somewhat complex and would need to parse an > entire language. -- 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
[GitHub] [qpid-proton] asfgit merged pull request #393: PROTON-2708: Introduce new proactor APIs that query batch
asfgit merged PR #393: URL: https://github.com/apache/qpid-proton/pull/393 -- 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] [Closed] (PROTON-2696) raw_connection_test.cpp:846:12: error: private field 'accept_' is not used [-Werror,-Wunused-private-field]
[
https://issues.apache.org/jira/browse/PROTON-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell closed PROTON-2696.
--
> raw_connection_test.cpp:846:12: error: private field 'accept_' is not used
> [-Werror,-Wunused-private-field]
> ---
>
> Key: PROTON-2696
> URL: https://issues.apache.org/jira/browse/PROTON-2696
> Project: Qpid Proton
> Issue Type: Bug
> Components: build, proton-c
>Affects Versions: proton-c-0.39.0
> Environment: Arm64 Ubuntu Focal on TravisCI
>Reporter: Jiri Daněk
>Priority: Major
>
> https://app.travis-ci.com/github/jiridanek/skupper-router/jobs/598829054#L950
> {noformat}
> /home/travis/build/jiridanek/skupper-router/qpid-proton/c/tests/raw_connection_test.cpp:846:12:
> error: private field 'accept_' is not used [-Werror,-Wunused-private-field]
> handler *accept_; // Handler for accepted connections
>^
> 1 error generated.
> {noformat}
--
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] (PROTON-2696) raw_connection_test.cpp:846:12: error: private field 'accept_' is not used [-Werror,-Wunused-private-field]
[
https://issues.apache.org/jira/browse/PROTON-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-2696:
---
Fix Version/s: (was: proton-c-0.39.0)
Removing fix-version as its test-only and the causing change/JIRA is already a
bug in the same release. Linked this issue as being part of it.
> raw_connection_test.cpp:846:12: error: private field 'accept_' is not used
> [-Werror,-Wunused-private-field]
> ---
>
> Key: PROTON-2696
> URL: https://issues.apache.org/jira/browse/PROTON-2696
> Project: Qpid Proton
> Issue Type: Bug
> Components: build, proton-c
>Affects Versions: proton-c-0.39.0
> Environment: Arm64 Ubuntu Focal on TravisCI
>Reporter: Jiri Daněk
>Priority: Major
>
> https://app.travis-ci.com/github/jiridanek/skupper-router/jobs/598829054#L950
> {noformat}
> /home/travis/build/jiridanek/skupper-router/qpid-proton/c/tests/raw_connection_test.cpp:846:12:
> error: private field 'accept_' is not used [-Werror,-Wunused-private-field]
> handler *accept_; // Handler for accepted connections
>^
> 1 error generated.
> {noformat}
--
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] (PROTON-2695) Epoll proactor raw connections hang on incomplete batches
[ https://issues.apache.org/jira/browse/PROTON-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2695. Resolution: Fixed > Epoll proactor raw connections hang on incomplete batches > - > > Key: PROTON-2695 > URL: https://issues.apache.org/jira/browse/PROTON-2695 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.38.0 >Reporter: Clifford Jansen >Assignee: Clifford Jansen >Priority: Major > Fix For: proton-c-0.39.0 > > > If an application returns a batch before draining all available events from > it, the internal state machine may not have completed the steps needed to > determine the correct polling events of interest, leaving the associated task > in a hung state. > This is particularly relevant for the Catch2 test harness using the proactor. -- 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] (PROTON-2695) Epoll proactor raw connections hang on incomplete batches
[ https://issues.apache.org/jira/browse/PROTON-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2695: --- Fix Version/s: proton-c-0.39.0 > Epoll proactor raw connections hang on incomplete batches > - > > Key: PROTON-2695 > URL: https://issues.apache.org/jira/browse/PROTON-2695 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.38.0 >Reporter: Clifford Jansen >Assignee: Clifford Jansen >Priority: Major > Fix For: proton-c-0.39.0 > > > If an application returns a batch before draining all available events from > it, the internal state machine may not have completed the steps needed to > determine the correct polling events of interest, leaving the associated task > in a hung state. > This is particularly relevant for the Catch2 test harness using the proactor. -- 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] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2663: --- Affects Version/s: proton-c-0.38.0 > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0, proton-c-0.38.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Assignee: Andrew Stitcher >Priority: Major > Labels: ssl > Fix For: proton-c-0.39.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- 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] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2663: --- Priority: Major (was: Blocker) > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Assignee: Andrew Stitcher >Priority: Major > Labels: ssl > Fix For: proton-c-0.39.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- 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] [Assigned] (PROTON-2663) class ssl_client_options does not have a constructor for a custom client certificate, and default certificate trust database
[ https://issues.apache.org/jira/browse/PROTON-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned PROTON-2663: -- Assignee: Andrew Stitcher > class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database > - > > Key: PROTON-2663 > URL: https://issues.apache.org/jira/browse/PROTON-2663 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.37.0 > Environment: Linux 64bit > Ubuntu 22.04: libqpid-proton-cpp12 0.22.0-5 (used for testing, not intended > for production) > Redhat, Oracle: qpid-proton-cpp-0.37.0-1.el8.x86_64 >Reporter: Marko Hrastovec >Assignee: Andrew Stitcher >Priority: Blocker > Labels: ssl > Fix For: proton-c-0.39.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > Class ssl_client_options does not have a constructor for a custom client > certificate, and default certificate trust database. > Out application has to present a custom certificate to the server, but the > server uses a certificate signed by a certificate authority (CA) that is > present in the systems default certificate trust database. > Curently, our only option to connect is to supply a dummy certificate trust > database, and use proton::ssl::ANONYMOUS_PEER which disables server check. In > that way, we skip an important check for a secure connection. That is > unacceptable for a production version of our application. Until we come to a > production version we must resolve that issue. That is why I marked it as a > blocker. > I have a patch, but I am not sure how to contribute it. I guess reporting is > a first step? -- 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] (PROTON-2704) [Python] The examples test hangs
[ https://issues.apache.org/jira/browse/PROTON-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2704. Resolution: Fixed > [Python] The examples test hangs > > > Key: PROTON-2704 > URL: https://issues.apache.org/jira/browse/PROTON-2704 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Running the python examples via the unittest in the examples directory hangs > at the various sync client tests. -- 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] (PROTON-2668) Change versions of Python used/supported
[ https://issues.apache.org/jira/browse/PROTON-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2668. Resolution: Fixed > Change versions of Python used/supported > > > Key: PROTON-2668 > URL: https://issues.apache.org/jira/browse/PROTON-2668 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > We currently support Python 3.6 upwards; this is an old and unsupported > version of python pretty much everywhere. > In particular some of the CI systems no longer even have this version which > is causing some build failures. > Let's change the supported versions to be 3.8 and up which covers pretty much > all supported LTS versions of Ubuntu (20.04, 22.04) -- 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] (PROTON-2699) Turn off proactor fdlimit test by default
[ https://issues.apache.org/jira/browse/PROTON-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2699. Resolution: Fixed > Turn off proactor fdlimit test by default > - > > Key: PROTON-2699 > URL: https://issues.apache.org/jira/browse/PROTON-2699 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.38.0 >Reporter: Clifford Jansen >Assignee: Clifford Jansen >Priority: Minor > Fix For: proton-c-0.39.0 > > > It has had many tweaks over the years yet remains sensitive to changes in OS > versions, Python versions, parallelism of the test, system resources... i.e. > it is flaky. Keep it around but off by default. -- 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
