[
https://issues.apache.org/jira/browse/PROTON-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631403#comment-14631403
]
ASF subversion and git services commented on PROTON-919:
Commit
[
https://issues.apache.org/jira/browse/PROTON-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed PROTON-919.
--
Resolution: Fixed
Fix Version/s: 0.10
commit 4ee726002804d7286a8c76b42e0a0717e0798822
Looking nice, good job :)
(same goes to Gordon as well for the inspiring material :p)
Robbie
On 14 July 2015 at 23:31, aconway acon...@redhat.com wrote:
C++ tutorial is mostly done, if that interests you
http://people.apache.org/~aconway/proton/
or check out cjansen-cpp-client.
FWIW, I'm currently swapping in enough context to confidently +1
PROTON-905, as well as hopefully answer a few related questions on the list.
--Rafael
On Fri, Jul 17, 2015 at 3:35 AM, Robbie Gemmell robbie.gemm...@gmail.com
wrote:
The are currently 11 unresolved JIRAs assigned a 0.10 fix-for:
I happened to be attempting the same on PROTON-905, though I stopped
short of actually hitting 'ship it' given the starting point of my
response ;)
On 17 July 2015 at 12:44, Rafael Schloming r...@alum.mit.edu wrote:
FWIW, I'm currently swapping in enough context to confidently +1
PROTON-905, as
[
https://issues.apache.org/jira/browse/PROTON-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-876:
--
Fix Version/s: (was: 0.10)
0.11
python examples installed under share are not
[
https://issues.apache.org/jira/browse/PROTON-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed PROTON-806.
-
Resolution: Cannot Reproduce
Closing for now; can reopen if it shows up again.
closing a blocking
On Thu, Jul 16, 2015 at 7:46 AM, Gordon Sim g...@redhat.com wrote:
On 07/16/2015 02:40 PM, aconway wrote:
Can someone who understand the proton use of refcounts please add some
doc comments to explain the semantics? Apologies if this is already
there and I missed it, tell me to RTFM.
I'm
Hello all,
when i try to download Proton 0.9.1 from
https://qpid.apache.org/releases/qpid-proton-0.9.1/index.html the archive i
download seems to contain 0.9.1 RC1 instead of the final version. This seems to
happen from multiple mirrors. Is it just the wrong directory name or is this
the
Hi Alex,
It is the wrong directory name inside the tar file. The 'rc1' bits
were voted as the final 0.9.1 release.
There was an issue (since corrected) with some release scripting
changes made just before the release, and the dirname issue wasn't
noticed until after everything was finished and
The are currently 11 unresolved JIRAs assigned a 0.10 fix-for:
http://s.apache.org/ytK
Of those, 4 are listed as blockers:
https://issues.apache.org/jira/browse/PROTON-905
Long-lived connections leak sessions and links
https://issues.apache.org/jira/browse/PROTON-923
[SASL] PN_TRANSPORT_ERROR
[
https://issues.apache.org/jira/browse/PROTON-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-803:
--
Fix Version/s: (was: 0.9)
0.11
Message codec improvements
Hi folks,
There are a bunch of unresolved JIRAs assigned with the 0.9 fix-for
(http://s.apache.org/VnH). I resolved or updated a few that were
obviously complete or not started in 0.9, but there are 17 remaining
that need attention from folks involved with the JIRA or who know
something about the
[
https://issues.apache.org/jira/browse/PROTON-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved PROTON-740.
---
Resolution: Fixed
idle timeouts repeat and the transport never closes
[
https://issues.apache.org/jira/browse/PROTON-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved PROTON-838.
---
Resolution: Fixed
proton-hawtdispatch cannot connect with SSL
Hi Gordon,
I did my best to dump some useful info on the refcounting stuff in the
other thread. I also posted a comment on the review. As I said there it
would be helpful to see the stack trace from the crash in order to figure
out if the fix is merely a workaround.
--Rafael
On Wed, Jul 15,
Still digesting the explanation (thanks!) but one follow up question:
On 07/17/2015 04:37 PM, Rafael Schloming wrote:
it isn't actually possible to use the object when there refcount is 0.
What is the purpose of the incref/decref pattern then, e.g. as used in
pn_session_free()? That is
On 07/17/2015 05:36 PM, Rafael Schloming wrote:
Hi Gordon,
I did my best to dump some useful info on the refcounting stuff in the
other thread. I also posted a comment on the review. As I said there it
would be helpful to see the stack trace from the crash in order to figure
out if the fix is
I'm having an issue with the pn_messenger_settle API that I'd like to see if
you can clear up. We have a loop that uses non-blocking sends to transmit
messages and attempts to settle them when they come back from the server. The
server replies in non-sequential order and when we attempt to
On Fri, Jul 17, 2015 at 10:45 AM, Gordon Sim g...@redhat.com wrote:
Still digesting the explanation (thanks!) but one follow up question:
On 07/17/2015 04:37 PM, Rafael Schloming wrote:
it isn't actually possible to use the object when there refcount is 0.
What is the purpose of the
[
https://issues.apache.org/jira/browse/PROTON-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed PROTON-864.
--
Resolution: Fixed
Fix Version/s: 0.10
This is a duplicate of PROTON-842
don't crash
On 07/17/2015 08:11 PM, Rafael Schloming wrote:
On Fri, Jul 17, 2015 at 10:45 AM, Gordon Sim g...@redhat.com wrote:
Still digesting the explanation (thanks!) but one follow up question:
On 07/17/2015 04:37 PM, Rafael Schloming wrote:
it isn't actually possible to use the object when there
On 07/17/2015 04:37 PM, Rafael Schloming wrote:
Are they really returned with a ref count of 0?
No, indeed they are not. I missed the fact that the finalizer will run
before the object is returned to the application.
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122435378
It looks to me that the appveyor failure is due to some incidental issue
with the service.
---
If your project is set up for it, you can reply to this email and
GitHub user astitcher opened a pull request:
https://github.com/apache/qpid-proton/pull/47
NO-JIRA: Change travis configuration to use container based builds
This is specifically for comment from @dnwe - I'm proposing to change the
travis build config to use containers, but I've
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122437243
Ok. :+1. Ship it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122435936
Changes look reasonable to me. Faster sudoless docker builds would be cool.
You dropped the PYTHON_DIRS bit which was for tox to locate the various
Python
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122436754
The tox thing is the bit I'm shakiest about - it seems to find 3 out of
the 4 pythons (not 2.6 I think) for some reason. I experimented with a
matrix test
28 matches
Mail list logo
