[jira] [Commented] (PROTON-2794) [protonj2] Transfer ID does not wrap as expected

[ https://issues.apache.org/jira/browse/PROTON-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824289#comment-17824289 ] Arnaud Cogoluègnes commented on PROTON-2794: Thanks for the follow-up. I confirm it is

[jira] [Commented] (PROTON-2802) [protonj2] Add additional validation scripting to the AMQP test peer

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

[jira] [Commented] (PROTON-2792) [cpp] Segmentation fault in container::impl::run_timer_jobs

[ https://issues.apache.org/jira/browse/PROTON-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824146#comment-17824146 ] ASF GitHub Bot commented on PROTON-2792: astitcher commented on PR #421: URL:

Re: [PR] PROTON-2792: [cpp] Segmentation fault in container::impl::run_timer_jobs [qpid-proton]

astitcher commented on PR #421: URL: https://github.com/apache/qpid-proton/pull/421#issuecomment-1981610822 There is a clear thread safety violation in ```run_timer_jobs`` use of ```is_active_``` without using the appropriate lock - in fact this is so obvious that I'm puzzled we haven't