[jira] [Commented] (DISPATCH-1089) Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus
[ https://issues.apache.org/jira/browse/DISPATCH-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558858#comment-16558858 ] ASF subversion and git services commented on DISPATCH-1089: --- Commit 7a77931a16d272fda58c4b7b854de041fa6df1e7 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7a77931 ] DISPATCH-1089 - Send empty, not null, router-side termini with auto-link attaches. > Dispatch creates sender autolinks with null source terminus and receiver > autolinks with null target terminus > > > Key: DISPATCH-1089 > URL: https://issues.apache.org/jira/browse/DISPATCH-1089 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.1.0, 1.2.0 >Reporter: Ganesh Murthy >Assignee: Ted Ross >Priority: Major > Fix For: 1.3.0 > > Attachments: qdrouterd-auto-link.conf > > > Steps to reproduce > Start the Qpid Java Broker > Create a queue called myQueue > Start the Dispatch Router with the attached config file > The router sends the following attach to the Broker > {noformat} > 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, > rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, > expiry-policy=:"link-detach", timeout=0, dynamic=false], > initial-delivery-count=0, max-message-size=0]{noformat} > The broker responds with an attach followed by a detach. > {noformat} > 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] > 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) > [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", > description="received Attach with remote null terminus."]] > {noformat} > The outgoing sender (router) seems to have a target but null source terminus > > According to the spec - > If no source is specified on an outgoing link, then there is no source > currently attached to the link. A link with no source will never produce > outgoing messages. > If no target is specified on an incoming link, then there is no target > currently attached to the link. A link with no target will never permit > incoming messages. > > The router must specify a source terminus when creating sending links and > must specify target terminus when creating receiving links -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1089) Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus
[ https://issues.apache.org/jira/browse/DISPATCH-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-1089. Resolution: Fixed > Dispatch creates sender autolinks with null source terminus and receiver > autolinks with null target terminus > > > Key: DISPATCH-1089 > URL: https://issues.apache.org/jira/browse/DISPATCH-1089 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.1.0, 1.2.0 >Reporter: Ganesh Murthy >Assignee: Ted Ross >Priority: Major > Fix For: 1.3.0 > > Attachments: qdrouterd-auto-link.conf > > > Steps to reproduce > Start the Qpid Java Broker > Create a queue called myQueue > Start the Dispatch Router with the attached config file > The router sends the following attach to the Broker > {noformat} > 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, > rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, > expiry-policy=:"link-detach", timeout=0, dynamic=false], > initial-delivery-count=0, max-message-size=0]{noformat} > The broker responds with an attach followed by a detach. > {noformat} > 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] > 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) > [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", > description="received Attach with remote null terminus."]] > {noformat} > The outgoing sender (router) seems to have a target but null source terminus > > According to the spec - > If no source is specified on an outgoing link, then there is no source > currently attached to the link. A link with no source will never produce > outgoing messages. > If no target is specified on an incoming link, then there is no target > currently attached to the link. A link with no target will never permit > incoming messages. > > The router must specify a source terminus when creating sending links and > must specify target terminus when creating receiving links -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1089) Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus
[ https://issues.apache.org/jira/browse/DISPATCH-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1089: Attachment: qdrouterd-auto-link.conf > Dispatch creates sender autolinks with null source terminus and receiver > autolinks with null target terminus > > > Key: DISPATCH-1089 > URL: https://issues.apache.org/jira/browse/DISPATCH-1089 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.1.0, 1.2.0 >Reporter: Ganesh Murthy >Assignee: Ted Ross >Priority: Major > Fix For: 1.3.0 > > Attachments: qdrouterd-auto-link.conf > > > Steps to reproduce > Start the Qpid Java Broker > Create a queue called myQueue > Start the Dispatch Router with the attached config file > The router sends the following attach to the Broker > {noformat} > 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, > rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, > expiry-policy=:"link-detach", timeout=0, dynamic=false], > initial-delivery-count=0, max-message-size=0]{noformat} > The broker responds with an attach followed by a detach. > {noformat} > 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] > 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) > [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", > description="received Attach with remote null terminus."]] > {noformat} > The outgoing sender (router) seems to have a target but null source terminus > > According to the spec - > If no source is specified on an outgoing link, then there is no source > currently attached to the link. A link with no source will never produce > outgoing messages. > If no target is specified on an incoming link, then there is no target > currently attached to the link. A link with no target will never permit > incoming messages. > > The router must specify a source terminus when creating sending links and > must specify target terminus when creating receiving links -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1089) Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus
[ https://issues.apache.org/jira/browse/DISPATCH-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1089: Description: Steps to reproduce Start the Qpid Java Broker Create a queue called myQueue Start the Dispatch Router with the attached config file The router sends the following attach to the Broker {noformat} 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, expiry-policy=:"link-detach", timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]{noformat} The broker responds with an attach followed by a detach. {noformat} 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", description="received Attach with remote null terminus."]] {noformat} The outgoing sender (router) seems to have a target but null source terminus According to the spec - If no source is specified on an outgoing link, then there is no source currently attached to the link. A link with no source will never produce outgoing messages. If no target is specified on an incoming link, then there is no target currently attached to the link. A link with no target will never permit incoming messages. The router must specify a source terminus when creating sending links and must specify target terminus when creating receiving links was: Steps to reproduce Start the Qpid Java Broker Start the Dispatch Router with the attached config file The router sends the following attach to the Broker {noformat} 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, expiry-policy=:"link-detach", timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]{noformat} The broker responds with an attach followed by a detach. {noformat} 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", description="received Attach with remote null terminus."]] {noformat} The outgoing sender (router) seems to have a target but null source terminus According to the spec - If no source is specified on an outgoing link, then there is no source currently attached to the link. A link with no source will never produce outgoing messages. If no target is specified on an incoming link, then there is no target currently attached to the link. A link with no target will never permit incoming messages. The router must specify a source terminus when creating sending links and must specify target terminus when creating receiving links > Dispatch creates sender autolinks with null source terminus and receiver > autolinks with null target terminus > > > Key: DISPATCH-1089 > URL: https://issues.apache.org/jira/browse/DISPATCH-1089 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.1.0, 1.2.0 >Reporter: Ganesh Murthy >Assignee: Ted Ross >Priority: Major > Fix For: 1.3.0 > > > Steps to reproduce > Start the Qpid Java Broker > Create a queue called myQueue > Start the Dispatch Router with the attached config file > The router sends the following attach to the Broker > {noformat} > 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, > rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, > expiry-policy=:"link-detach", timeout=0, dynamic=false], > initial-delivery-count=0, max-message-size=0]{noformat} > The broker responds with an attach followed by a detach. > {noformat} > 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] > 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) > [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", > description="received Attach with remote null terminus."]] > {noformat} > The outgoing sender (router) seems to have a target but null source terminus > > According to the spec - > If no source is specified on an outgoing link, then there is no source > currently attached to
[jira] [Assigned] (DISPATCH-1089) Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus
[ https://issues.apache.org/jira/browse/DISPATCH-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-1089: -- Assignee: Ted Ross (was: Ganesh Murthy) > Dispatch creates sender autolinks with null source terminus and receiver > autolinks with null target terminus > > > Key: DISPATCH-1089 > URL: https://issues.apache.org/jira/browse/DISPATCH-1089 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.1.0, 1.2.0 >Reporter: Ganesh Murthy >Assignee: Ted Ross >Priority: Major > Fix For: 1.3.0 > > > Steps to reproduce > Start the Qpid Java Broker > Start the Dispatch Router with the attached config file > The router sends the following attach to the Broker > {noformat} > 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, > rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, > expiry-policy=:"link-detach", timeout=0, dynamic=false], > initial-delivery-count=0, max-message-size=0]{noformat} > The broker responds with an attach followed by a detach. > {noformat} > 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) > [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] > 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) > [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", > description="received Attach with remote null terminus."]] > {noformat} > The outgoing sender (router) seems to have a target but null source terminus > > According to the spec - > If no source is specified on an outgoing link, then there is no source > currently attached to the link. A link with no source will never produce > outgoing messages. > If no target is specified on an incoming link, then there is no target > currently attached to the link. A link with no target will never permit > incoming messages. > > The router must specify a source terminus when creating sending links and > must specify target terminus when creating receiving links -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1089) Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus
Ganesh Murthy created DISPATCH-1089: --- Summary: Dispatch creates sender autolinks with null source terminus and receiver autolinks with null target terminus Key: DISPATCH-1089 URL: https://issues.apache.org/jira/browse/DISPATCH-1089 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 1.2.0, 1.1.0 Reporter: Ganesh Murthy Assignee: Ganesh Murthy Fix For: 1.3.0 Steps to reproduce Start the Qpid Java Broker Start the Dispatch Router with the attached config file The router sends the following attach to the Broker {noformat} 2018-07-26 11:26:00.573105 +0200 SERVER (trace) [1]:0 -> @attach(18) [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, target=@target(41) [address="myTopic", durable=0, expiry-policy=:"link-detach", timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]{noformat} The broker responds with an attach followed by a detach. {noformat} 2018-07-26 11:26:00.604407 +0200 SERVER (trace) [1]:0 <- @attach(18) [name="qdlink.77HlwzdjtvX7pG1", handle=0, role=true] 2018-07-26 11:26:00.604429 +0200 SERVER (trace) [1]:0 <- @detach(22) [handle=0, closed=true, error=@error(29) [condition=:"amqp:invalid-field", description="received Attach with remote null terminus."]] {noformat} The outgoing sender (router) seems to have a target but null source terminus According to the spec - If no source is specified on an outgoing link, then there is no source currently attached to the link. A link with no source will never produce outgoing messages. If no target is specified on an incoming link, then there is no target currently attached to the link. A link with no target will never permit incoming messages. The router must specify a source terminus when creating sending links and must specify target terminus when creating receiving links -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #133: PROTON-1796 branch for automated periodic Coverity S...
Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/133 I have to agree. Without the ability to have periodic travis build, there won't be a point. Closing the PR, then. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[ https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558489#comment-16558489 ] ASF GitHub Bot commented on PROTON-1796: Github user jdanekrh closed the pull request at: https://github.com/apache/qpid-proton/pull/133 > Automated periodic Coverity Scan runs > - > > Key: PROTON-1796 > URL: https://issues.apache.org/jira/browse/PROTON-1796 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.21.0 >Reporter: Jiri Daněk >Priority: Major > > The attached commit could be added as a new branch. Then, TravisCI can be set > up > to build it daily (or weekly). > What it does is that it > * checks out the current master branch > * builds it under the Coverity tool > * submits the build to Coverity Scan > The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one. > The new branch would need to be created. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[ https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558488#comment-16558488 ] ASF GitHub Bot commented on PROTON-1796: Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/133 I have to agree. Without the ability to have periodic travis build, there won't be a point. Closing the PR, then. > Automated periodic Coverity Scan runs > - > > Key: PROTON-1796 > URL: https://issues.apache.org/jira/browse/PROTON-1796 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.21.0 >Reporter: Jiri Daněk >Priority: Major > > The attached commit could be added as a new branch. Then, TravisCI can be set > up > to build it daily (or weekly). > What it does is that it > * checks out the current master branch > * builds it under the Coverity tool > * submits the build to Coverity Scan > The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one. > The new branch would need to be created. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #133: PROTON-1796 branch for automated periodic Cov...
Github user jdanekrh closed the pull request at: https://github.com/apache/qpid-proton/pull/133 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[ https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558484#comment-16558484 ] ASF GitHub Bot commented on PROTON-1796: Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/133 I meant the PR probably doesnt make sense, i.e we wouldnt have a branch here, which it seems you agree with. > Automated periodic Coverity Scan runs > - > > Key: PROTON-1796 > URL: https://issues.apache.org/jira/browse/PROTON-1796 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.21.0 >Reporter: Jiri Daněk >Priority: Major > > The attached commit could be added as a new branch. Then, TravisCI can be set > up > to build it daily (or weekly). > What it does is that it > * checks out the current master branch > * builds it under the Coverity tool > * submits the build to Coverity Scan > The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one. > The new branch would need to be created. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #133: PROTON-1796 branch for automated periodic Coverity S...
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/133 I meant the PR probably doesnt make sense, i.e we wouldnt have a branch here, which it seems you agree with. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[ https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558459#comment-16558459 ] ASF GitHub Bot commented on PROTON-1796: Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/133 It does not have to be placed on this mirror. The Artemis coverity run is under /msgqe/ organization on github. The only requirement is that the coverity token needs to be uploaded to travis under that specific account. So, for example, if I was given rights on coverity website to upload new builds for the project, I would be able to set up the coverity build. (That is exactly how it is working for Artemis right now.) > Automated periodic Coverity Scan runs > - > > Key: PROTON-1796 > URL: https://issues.apache.org/jira/browse/PROTON-1796 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.21.0 >Reporter: Jiri Daněk >Priority: Major > > The attached commit could be added as a new branch. Then, TravisCI can be set > up > to build it daily (or weekly). > What it does is that it > * checks out the current master branch > * builds it under the Coverity tool > * submits the build to Coverity Scan > The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one. > The new branch would need to be created. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #133: PROTON-1796 branch for automated periodic Coverity S...
Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/133 It does not have to be placed on this mirror. The Artemis coverity run is under /msgqe/ organization on github. The only requirement is that the coverity token needs to be uploaded to travis under that specific account. So, for example, if I was given rights on coverity website to upload new builds for the project, I would be able to set up the coverity build. (That is exactly how it is working for Artemis right now.) --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[ https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558454#comment-16558454 ] ASF GitHub Bot commented on PROTON-1796: Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/133 I don't think we have ability to configure periodic builds in Travis on this mirror, over which we have limited control in which case this doesn't really make sense. > Automated periodic Coverity Scan runs > - > > Key: PROTON-1796 > URL: https://issues.apache.org/jira/browse/PROTON-1796 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.21.0 >Reporter: Jiri Daněk >Priority: Major > > The attached commit could be added as a new branch. Then, TravisCI can be set > up > to build it daily (or weekly). > What it does is that it > * checks out the current master branch > * builds it under the Coverity tool > * submits the build to Coverity Scan > The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one. > The new branch would need to be created. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #133: PROTON-1796 branch for automated periodic Coverity S...
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton/pull/133 I don't think we have ability to configure periodic builds in Travis on this mirror, over which we have limited control in which case this doesn't really make sense. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[ https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558379#comment-16558379 ] ASF GitHub Bot commented on PROTON-1796: Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/133 @ssorj The coverity PR for daily (weekly) build. This is the same thing that is set up for Artemis, https://github.com/msgqe/travisci/tree/activemq-artemis-coverity. > Automated periodic Coverity Scan runs > - > > Key: PROTON-1796 > URL: https://issues.apache.org/jira/browse/PROTON-1796 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.21.0 >Reporter: Jiri Daněk >Priority: Major > > The attached commit could be added as a new branch. Then, TravisCI can be set > up > to build it daily (or weekly). > What it does is that it > * checks out the current master branch > * builds it under the Coverity tool > * submits the build to Coverity Scan > The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one. > The new branch would need to be created. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #133: PROTON-1796 branch for automated periodic Coverity S...
Github user jdanekrh commented on the issue: https://github.com/apache/qpid-proton/pull/133 @ssorj The coverity PR for daily (weekly) build. This is the same thing that is set up for Artemis, https://github.com/msgqe/travisci/tree/activemq-artemis-coverity. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8219) [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 authentication providers per connection basis
[ https://issues.apache.org/jira/browse/QPID-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558246#comment-16558246 ] ASF subversion and git services commented on QPID-8219: --- Commit 0b3cefaeee90949b52c54bd9150e077525c9d3c7 in qpid-broker-j's branch refs/heads/6.1.x from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=0b3cefa ] QPID-8219: [Broker-J] Cache authentication results for the same remote hosts and credentials (cherry picked from commit 6fd5156b6a16381839ac86fce1c7ce2aabe542dc) > [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 > authentication providers per connection basis > --- > > Key: QPID-8219 > URL: https://issues.apache.org/jira/browse/QPID-8219 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2, > qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, > qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0, > qpid-java-broker-7.0.7 > > > SimpleLdap and OAUTH2 authentication providers were supposed to cache > authentication results per remote host basis. Thus, when connections are made > from the same host using the same credentials, the cached authentication > result should be reused. The current caching approach takes into > consideration an ephemeral port of the connection. As result, a new > connection from the same host with the same credentials cannot reuse previous > authentication result due to a different ephemeral port. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8219) [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 authentication providers per connection basis
[ https://issues.apache.org/jira/browse/QPID-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558216#comment-16558216 ] ASF subversion and git services commented on QPID-8219: --- Commit 6fd5156b6a16381839ac86fce1c7ce2aabe542dc in qpid-broker-j's branch refs/heads/7.0.x from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=6fd5156 ] QPID-8219: [Broker-J] Cache authentication results for the same remote hosts and credentials > [Broker-J] Authentication results are cached in SimpleLdap and OAUTH2 > authentication providers per connection basis > --- > > Key: QPID-8219 > URL: https://issues.apache.org/jira/browse/QPID-8219 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, > qpid-java-broker-7.0.2, qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2, > qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, > qpid-java-broker-7.0.1, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-6.1.7, qpid-java-broker-7.1.0, > qpid-java-broker-7.0.7 > > > SimpleLdap and OAUTH2 authentication providers were supposed to cache > authentication results per remote host basis. Thus, when connections are made > from the same host using the same credentials, the cached authentication > result should be reused. The current caching approach takes into > consideration an ephemeral port of the connection. As result, a new > connection from the same host with the same credentials cannot reuse previous > authentication result due to a different ephemeral port. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org