[jira] [Commented] (PROTON-969) Cyrus SASL module calls sasl_server_init once for every incoming connection

[ https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649213#comment-14649213 ] Dominic Evans commented on PROTON-969: -- It seems like these calls would increment a r

[jira] [Created] (PROTON-931) proton-j: unable to determine if LINK_REMOTE_DETACH happened in response to a local detach

Dominic Evans created PROTON-931: Summary: proton-j: unable to determine if LINK_REMOTE_DETACH happened in response to a local detach Key: PROTON-931 URL: https://issues.apache.org/jira/browse/PROTON-931

[jira] [Commented] (PROTON-885) Allow setup.py to bundle qpid-proton

[ https://issues.apache.org/jira/browse/PROTON-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542731#comment-14542731 ] Dominic Evans commented on PROTON-885: -- Whilst I really like the idea of being able t

[jira] [Resolved] (PROTON-844) proton-j: ArrayIndexOutOfBounds exception if remote peer sends a handle >1024

[ https://issues.apache.org/jira/browse/PROTON-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-844. -- Resolution: Fixed > proton-j: ArrayIndexOutOfBounds exception if remote peer sends a handle >102

[jira] [Created] (PROTON-844) proton-j: ArrayIndexOutOfBounds exception if remote peer sends a handle >1024

Dominic Evans created PROTON-844: Summary: proton-j: ArrayIndexOutOfBounds exception if remote peer sends a handle >1024 Key: PROTON-844 URL: https://issues.apache.org/jira/browse/PROTON-844 Project:

[jira] [Created] (PROTON-843) proton-j: Transport advertises idle timeout as-is whereas proton-c halves it before

Dominic Evans created PROTON-843: Summary: proton-j: Transport advertises idle timeout as-is whereas proton-c halves it before Key: PROTON-843 URL: https://issues.apache.org/jira/browse/PROTON-843 Pro

[jira] [Updated] (PROTON-834) proton-j: UTF-8 encoder reporting some three byte characters as invalid surrogates

[ https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-834: - Fix Version/s: (was: 0.9) > proton-j: UTF-8 encoder reporting some three byte characters as in

[jira] [Reopened] (PROTON-834) proton-j: UTF-8 encoder reporting some three byte characters as invalid surrogates

[ https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reopened PROTON-834: -- Assignee: Dominic Evans > proton-j: UTF-8 encoder reporting some three byte characters as inva

[jira] [Resolved] (PROTON-834) proton-j: UTF-8 encoder reporting some three byte characters as invalid surrogates

[ https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-834. -- Resolution: Fixed Pushed c65e897 > proton-j: UTF-8 encoder reporting some three byte character

[jira] [Created] (PROTON-834) proton-j: UTF-8 encoder reporting some three byte characters as invalid surrogates

Dominic Evans created PROTON-834: Summary: proton-j: UTF-8 encoder reporting some three byte characters as invalid surrogates Key: PROTON-834 URL: https://issues.apache.org/jira/browse/PROTON-834 Proj

[jira] [Resolved] (PROTON-832) messenger: next_drain is not reset for "manual" link credit mode in messenger

[ https://issues.apache.org/jira/browse/PROTON-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-832. -- Resolution: Fixed > messenger: next_drain is not reset for "manual" link credit mode in messenge

[jira] [Created] (PROTON-832) messenger: next_drain is not reset for "manual" link credit mode in messenger

Dominic Evans created PROTON-832: Summary: messenger: next_drain is not reset for "manual" link credit mode in messenger Key: PROTON-832 URL: https://issues.apache.org/jira/browse/PROTON-832 Project:

[jira] [Assigned] (PROTON-832) messenger: next_drain is not reset for "manual" link credit mode in messenger

[ https://issues.apache.org/jira/browse/PROTON-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-832: Assignee: Dominic Evans > messenger: next_drain is not reset for "manual" link credit mode

[jira] [Closed] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-548. > Proton-C driver and URL Parsers don't support AF_INET6 (IPv6) > --

[jira] [Resolved] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-548. -- Resolution: Fixed Just noticed that the windows fix was comitted by [~chug] under commit b4fbb15

[jira] [Resolved] (PROTON-154) proton-j: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-154. -- Resolution: Fixed Fix Version/s: 0.9 > proton-j: link attach, detach, attach sequence on

[jira] [Commented] (PROTON-154) proton-j: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314293#comment-14314293 ] Dominic Evans commented on PROTON-154: -- hit this issue on proton-j in HEAD, no longer

[jira] [Updated] (PROTON-154) proton-j: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-154: - Summary: proton-j: link attach, detach, attach sequence on single session does not result in a new

[jira] [Assigned] (PROTON-154) link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

[ https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-154: Assignee: Dominic Evans > link attach, detach, attach sequence on single session does not r

[jira] [Commented] (PROTON-775) ruby: message annotations send from a ruby client are invalid

[ https://issues.apache.org/jira/browse/PROTON-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309067#comment-14309067 ] Dominic Evans commented on PROTON-775: -- [~mcpierce] do you have any thoughts of how w

[jira] [Assigned] (PROTON-490) [proton-c] Python binding fails to link with Python 3 libraries

[ https://issues.apache.org/jira/browse/PROTON-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-490: Assignee: Dominic Evans > [proton-c] Python binding fails to link with Python 3 libraries >

[jira] [Resolved] (PROTON-483) detach with closed=false (or unspecified) not handled

[ https://issues.apache.org/jira/browse/PROTON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-483. -- Resolution: Fixed I believe this is fixed by PROTON-677 > detach with closed=false (or unspecif

[jira] [Assigned] (PROTON-483) detach with closed=false (or unspecified) not handled

[ https://issues.apache.org/jira/browse/PROTON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-483: Assignee: Dominic Evans > detach with closed=false (or unspecified) not handled > -

[jira] [Resolved] (PROTON-737) [PATCH] ruby: StateError not included in exceptions

[ https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-737. -- Resolution: Fixed Fix Version/s: 0.9 > [PATCH] ruby: StateError not included in exception

[jira] [Closed] (PROTON-737) [PATCH] ruby: StateError not included in exceptions

[ https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-737. > [PATCH] ruby: StateError not included in exceptions >

[jira] [Assigned] (PROTON-737) [PATCH] ruby: StateError not included in exceptions

[ https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-737: Assignee: Dominic Evans (was: Darryl L. Pierce) > [PATCH] ruby: StateError not included in

[jira] [Closed] (PROTON-814) proton-c: pn_selector_select caches its return code from a previous error

[ https://issues.apache.org/jira/browse/PROTON-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-814. > proton-c: pn_selector_select caches its return code from a previous error > --

[jira] [Resolved] (PROTON-814) proton-c: pn_selector_select caches its return code from a previous error

[ https://issues.apache.org/jira/browse/PROTON-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-814. -- Resolution: Fixed Fix Version/s: 0.9 > proton-c: pn_selector_select caches its return cod

[jira] [Created] (PROTON-814) proton-c: pn_selector_select caches its return code from a previous error

Dominic Evans created PROTON-814: Summary: proton-c: pn_selector_select caches its return code from a previous error Key: PROTON-814 URL: https://issues.apache.org/jira/browse/PROTON-814 Project: Qpid

[jira] [Closed] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-751. > [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error > --

[jira] [Assigned] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-751: Assignee: Dominic Evans > [PATCH] proton-c: pn_connect failures aren't exposed via messenge

[jira] [Resolved] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-751. -- Resolution: Fixed Fix Version/s: 0.9 fixed in b9423d4 > [PATCH] proton-c: pn_connect fai

[jira] [Closed] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-757. > [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards > -

[jira] [Resolved] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-757. -- Resolution: Fixed Fix Version/s: 0.9 Pushed under 78e54ee > [PATCH] proton-c: transport

[jira] [Assigned] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-757: Assignee: Dominic Evans > [PATCH] proton-c: transport errors are output to stderr in 0.8 on

[jira] [Created] (PROTON-776) proton-j: Message.decode doesn't validate all data types?

Dominic Evans created PROTON-776: Summary: proton-j: Message.decode doesn't validate all data types? Key: PROTON-776 URL: https://issues.apache.org/jira/browse/PROTON-776 Project: Qpid Proton

[jira] [Created] (PROTON-775) ruby: message annotations send from a ruby client are invalid

Dominic Evans created PROTON-775: Summary: ruby: message annotations send from a ruby client are invalid Key: PROTON-775 URL: https://issues.apache.org/jira/browse/PROTON-775 Project: Qpid Proton

[jira] [Created] (PROTON-763) proton-c: pn_messenger_stop closes all links (detach w/ close=true) regardless of TTL / expiry

Dominic Evans created PROTON-763: Summary: proton-c: pn_messenger_stop closes all links (detach w/ close=true) regardless of TTL / expiry Key: PROTON-763 URL: https://issues.apache.org/jira/browse/PROTON-763

[jira] [Updated] (PROTON-763) proton-c: pn_messenger_stop closes all links (detach w/ close=true) regardless of TTL / expiry

[ https://issues.apache.org/jira/browse/PROTON-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-763: - Description: As discussed on IRC. https://issues.apache.org/jira/browse/PROTON-677 (git commit 1

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-548: - Attachment: (was: 08_fix_ipv6_windows.patch) > Proton-C driver and URL Parsers don't support A

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-548: - Attachment: 08_fix_ipv6_windows.patch patch rebased against 0.8 > Proton-C driver and URL Parsers

[jira] [Updated] (PROTON-758) proton-c: assertion failure when SASL fails (PN_SASL_FAIL)

[ https://issues.apache.org/jira/browse/PROTON-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-758: - Description: As discussed on IRC When SASL negotiation fails (e.g., wrong type, bad user+pass etc

[jira] [Created] (PROTON-758) proton-c: assertion failure when SASL fails (PN_SASL_FAIL)

Dominic Evans created PROTON-758: Summary: proton-c: assertion failure when SASL fails (PN_SASL_FAIL) Key: PROTON-758 URL: https://issues.apache.org/jira/browse/PROTON-758 Project: Qpid Proton

[jira] [Updated] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-757: - Attachment: 0001-Don-t-trace-transport-errors-unless-PN_TRACE-set.patch patch attached > [PATCH]

[jira] [Created] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

Dominic Evans created PROTON-757: Summary: [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards Key: PROTON-757 URL: https://issues.apache.org/jira/browse/PROTON-757 Project: Qpid Pr

[jira] [Commented] (PROTON-752) Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations

[ https://issues.apache.org/jira/browse/PROTON-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224422#comment-14224422 ] Dominic Evans commented on PROTON-752: -- So I can see that this might be a useful thin

[jira] [Commented] (PROTON-752) Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations

[ https://issues.apache.org/jira/browse/PROTON-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223514#comment-14223514 ] Dominic Evans commented on PROTON-752: -- [~mcpierce] so I had a look at the patch, but

[jira] [Commented] (PROTON-752) Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations

[ https://issues.apache.org/jira/browse/PROTON-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219564#comment-14219564 ] Dominic Evans commented on PROTON-752: -- Yeah I similarly didn't see any built in supp

[jira] [Commented] (PROTON-752) Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations

[ https://issues.apache.org/jira/browse/PROTON-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218434#comment-14218434 ] Dominic Evans commented on PROTON-752: -- No I mean whenever a Cproton call won't retur

[jira] [Created] (PROTON-752) Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations

Dominic Evans created PROTON-752: Summary: Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations Key: PROTON-752 URL: https://issues.apache.org/jira/browse/PROTON-752 Project

[jira] [Updated] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-751: - Attachment: 0001-If-pn_connect-fails-copy-io-error-to-messenger.patch patch attached > [PATCH] pr

[jira] [Created] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error

Dominic Evans created PROTON-751: Summary: [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error Key: PROTON-751 URL: https://issues.apache.org/jira/browse/PROTON-751 Project: Qpid

[jira] [Updated] (PROTON-748) [PATCH] ruby: user doesn't have access to set settlement modes or messenger flags

[ https://issues.apache.org/jira/browse/PROTON-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-748: - Attachment: 0001-Add-support-for-Messenger-snd-rcv-modes-and-flags.patch patch attached > [PATCH]

[jira] [Created] (PROTON-748) [PATCH] ruby: user doesn't have access to set settlement modes or messenger flags

Dominic Evans created PROTON-748: Summary: [PATCH] ruby: user doesn't have access to set settlement modes or messenger flags Key: PROTON-748 URL: https://issues.apache.org/jira/browse/PROTON-748 Proje

[jira] [Updated] (PROTON-743) [PATCH] ruby: user doesn't have access to clear messenger error object

[ https://issues.apache.org/jira/browse/PROTON-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-743: - Attachment: 0001-Wrapper-pn_error-so-user-has-more-control-over-it.patch patch attached. > [PATCH

[jira] [Created] (PROTON-743) [PATCH] ruby: user doesn't have access to clear messenger error object

Dominic Evans created PROTON-743: Summary: [PATCH] ruby: user doesn't have access to clear messenger error object Key: PROTON-743 URL: https://issues.apache.org/jira/browse/PROTON-743 Project: Qpid Pr

[jira] [Updated] (PROTON-739) [PATCH] ruby: update messenger#subscribe to accept TTL

[ https://issues.apache.org/jira/browse/PROTON-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-739: - Attachment: 0001-ruby-update-messenger-subscribe-to-accept-TTL.patch > [PATCH] ruby: update messen

[jira] [Created] (PROTON-739) [PATCH] ruby: update messenger#subscribe to accept TTL

Dominic Evans created PROTON-739: Summary: [PATCH] ruby: update messenger#subscribe to accept TTL Key: PROTON-739 URL: https://issues.apache.org/jira/browse/PROTON-739 Project: Qpid Proton Is

[jira] [Created] (PROTON-738) Debian + Ubuntu Packages need updating to 0.8

Dominic Evans created PROTON-738: Summary: Debian + Ubuntu Packages need updating to 0.8 Key: PROTON-738 URL: https://issues.apache.org/jira/browse/PROTON-738 Project: Qpid Proton Issue Type:

[jira] [Commented] (PROTON-634) Packages are needed for Ubuntu Precise (12 LTS)

[ https://issues.apache.org/jira/browse/PROTON-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200916#comment-14200916 ] Dominic Evans commented on PROTON-634: -- [~kgiusti] it seems this has already been fix

[jira] [Commented] (PROTON-736) ruby: unable to send binary data?

[ https://issues.apache.org/jira/browse/PROTON-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200052#comment-14200052 ] Dominic Evans commented on PROTON-736: -- [~mcpierce] tested and confirmed working as d

[jira] [Commented] (PROTON-736) ruby: unable to send binary data?

[ https://issues.apache.org/jira/browse/PROTON-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196358#comment-14196358 ] Dominic Evans commented on PROTON-736: -- [~mcpierce] as discussed on IRC The problem

[jira] [Updated] (PROTON-737) [PATCH] ruby: StateError not included in exceptions

[ https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-737: - Attachment: 42_add_missing_exception_to_ruby_bindings.patch > [PATCH] ruby: StateError not include

[jira] [Created] (PROTON-737) [PATCH] ruby: StateError not included in exceptions

Dominic Evans created PROTON-737: Summary: [PATCH] ruby: StateError not included in exceptions Key: PROTON-737 URL: https://issues.apache.org/jira/browse/PROTON-737 Project: Qpid Proton Issue

[jira] [Created] (PROTON-736) ruby: unable to send binary data?

Dominic Evans created PROTON-736: Summary: ruby: unable to send binary data? Key: PROTON-736 URL: https://issues.apache.org/jira/browse/PROTON-736 Project: Qpid Proton Issue Type: Bug

[jira] [Commented] (PROTON-725) pni_parse_url does not properly handle Base64 in URL

[ https://issues.apache.org/jira/browse/PROTON-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182596#comment-14182596 ] Dominic Evans commented on PROTON-725: -- [~E528527] this is what URL encoding was desi

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: 02_fix_stringtype_encode_decode.patch Patch refreshed. > proton-j: codec support for

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: (was: 02_fix_stringtype_encode_decode.patch) > proton-j: codec support for UTF-8 e

[jira] [Commented] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140480#comment-14140480 ] Dominic Evans commented on PROTON-576: -- A small bit of improvement with that optimiza

[jira] [Commented] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140439#comment-14140439 ] Dominic Evans commented on PROTON-576: -- [~gemmellr] not sure what machine I ran the p

[jira] [Updated] (PROTON-682) proton-c: a call to pn_messenger_stop can get into an infinite loop if the remote connection is severed

[ https://issues.apache.org/jira/browse/PROTON-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-682: - Attachment: 36_socket_hangup_fix_selector.h.patch 36_socket_hangup_fix_selector.c.p

[jira] [Created] (PROTON-682) proton-c: a call to pn_messenger_stop can get into an infinite loop if the remote connection is severed

Dominic Evans created PROTON-682: Summary: proton-c: a call to pn_messenger_stop can get into an infinite loop if the remote connection is severed Key: PROTON-682 URL: https://issues.apache.org/jira/browse/PROTON-

[jira] [Closed] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-610. > proton-c: messenger doesn't honour an advertised remote idle timeout > ---

[jira] [Closed] (PROTON-573) proton-c: Messenger appears to have hard-coded address limits of 1024

[ https://issues.apache.org/jira/browse/PROTON-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-573. > proton-c: Messenger appears to have hard-coded address limits of 1024 > --

[jira] [Closed] (PROTON-575) proton-j: LoggingProtocolTracer used by FrameWriter cannot be overridden

[ https://issues.apache.org/jira/browse/PROTON-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-575. > proton-j: LoggingProtocolTracer used by FrameWriter cannot be overridden > ---

[jira] [Closed] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

[ https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-611. > [proton-c] transport buffer increased to peer's max frame size if initial > output_size is not enough

[jira] [Resolved] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map->load_factor`

[ https://issues.apache.org/jira/browse/PROTON-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-681. -- Resolution: Duplicate Closing as dupe. > proton-c: pni_map_ensure infinite loop if `load = map-

[jira] [Closed] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map->load_factor`

[ https://issues.apache.org/jira/browse/PROTON-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-681. > proton-c: pni_map_ensure infinite loop if `load = map->load_factor` >

[jira] [Commented] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map->load_factor`

[ https://issues.apache.org/jira/browse/PROTON-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129960#comment-14129960 ] Dominic Evans commented on PROTON-681: -- [~gemmellr] yep you're correct, looks like th

[jira] [Updated] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map->load_factor`

[ https://issues.apache.org/jira/browse/PROTON-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-681: - Attachment: 33_pni_map_ensure_bug_fix_object.c.patch > proton-c: pni_map_ensure infinite loop if `

[jira] [Created] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map->load_factor`

Dominic Evans created PROTON-681: Summary: proton-c: pni_map_ensure infinite loop if `load = map->load_factor` Key: PROTON-681 URL: https://issues.apache.org/jira/browse/PROTON-681 Project: Qpid Proto

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger->error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: (was: 02_set_pn_error_when_printing_connection_errors.patch) > proton-c: Messenger

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger->error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: 02_set_pn_error_when_printing_connection_errors.patch > proton-c: Messenger outputs er

[jira] [Updated] (PROTON-680) proton-c: Messenger doesn't provide a way of obtaining link or delivery information

[ https://issues.apache.org/jira/browse/PROTON-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-680: - Attachment: 31_access_messenger_deliveries_messenger.h.patch 30_access_messenger_de

[jira] [Created] (PROTON-680) proton-c: Messenger doesn't provide a way of obtaining link or delivery information

Dominic Evans created PROTON-680: Summary: proton-c: Messenger doesn't provide a way of obtaining link or delivery information Key: PROTON-680 URL: https://issues.apache.org/jira/browse/PROTON-680 Pro

[jira] [Updated] (PROTON-679) proton-c: add a "manual" link credit mode to Messenger

[ https://issues.apache.org/jira/browse/PROTON-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-679: - Attachment: 28_manual_link_management_messenger.c.patch > proton-c: add a "manual" link credit mod

[jira] [Created] (PROTON-679) proton-c: add a "manual" link credit mode to Messenger

Dominic Evans created PROTON-679: Summary: proton-c: add a "manual" link credit mode to Messenger Key: PROTON-679 URL: https://issues.apache.org/jira/browse/PROTON-679 Project: Qpid Proton Is

[jira] [Updated] (PROTON-678) proton-c: (Win 32-bit) pn_post_frame misinterprets variable argument data when ERROR is used

[ https://issues.apache.org/jira/browse/PROTON-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-678: - Attachment: 27_32bit_windows_fix_transport.c.patch > proton-c: (Win 32-bit) pn_post_frame misinter

[jira] [Created] (PROTON-678) proton-c: (Win 32-bit) pn_post_frame misinterprets variable argument data when ERROR is used

Dominic Evans created PROTON-678: Summary: proton-c: (Win 32-bit) pn_post_frame misinterprets variable argument data when ERROR is used Key: PROTON-678 URL: https://issues.apache.org/jira/browse/PROTON-678

[jira] [Created] (PROTON-677) proton-c: transport incorrectly detaches all links with closed=true by default

Dominic Evans created PROTON-677: Summary: proton-c: transport incorrectly detaches all links with closed=true by default Key: PROTON-677 URL: https://issues.apache.org/jira/browse/PROTON-677 Project:

[jira] [Updated] (PROTON-677) proton-c: transport incorrectly detaches all links with closed=true by default

[ https://issues.apache.org/jira/browse/PROTON-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-677: - Attachment: 26_stop_link_detach_closed_if_sub_ttl_transport.c.patch > proton-c: transport incorrec

[jira] [Updated] (PROTON-660) Fix openssl.c build on windows

[ https://issues.apache.org/jira/browse/PROTON-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-660: - Attachment: 25_openssl_fix_for_windows_platform.h.patch 25_openssl_fix_for_windows_

[jira] [Created] (PROTON-676) proton-c: transport layer SSL failures not propagated back to Messenger in pni_connection_readable

Dominic Evans created PROTON-676: Summary: proton-c: transport layer SSL failures not propagated back to Messenger in pni_connection_readable Key: PROTON-676 URL: https://issues.apache.org/jira/browse/PROTON-676

[jira] [Updated] (PROTON-676) proton-c: transport layer SSL failures not propagated back to Messenger in pni_connection_readable

[ https://issues.apache.org/jira/browse/PROTON-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-676: - Attachment: 24_ssl_transport_failure_fix_messenger.c.patch > proton-c: transport layer SSL failure

[jira] [Updated] (PROTON-675) proton-c: Messenger doesn't provide a way of setting the SSL peer authentication mode

[ https://issues.apache.org/jira/browse/PROTON-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-675: - Attachment: 23_add_messenger_set_ssl_peer_authentication_mode_method_messenger.h.patch

[jira] [Created] (PROTON-675) proton-c: Messenger doesn't provide a way of setting the SSL peer authentication mode

Dominic Evans created PROTON-675: Summary: proton-c: Messenger doesn't provide a way of setting the SSL peer authentication mode Key: PROTON-675 URL: https://issues.apache.org/jira/browse/PROTON-675 P

[jira] [Updated] (PROTON-674) proton-c: Messenger doesn't provide a way of setting the TTL on a subscription

[ https://issues.apache.org/jira/browse/PROTON-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-674: - Attachment: 22_add_messenger_subscribe_ttl_method_messenger.h.patch 22_add_messenge

[jira] [Created] (PROTON-674) proton-c: Messenger doesn't provide a way of setting the TTL on a subscription

Dominic Evans created PROTON-674: Summary: proton-c: Messenger doesn't provide a way of setting the TTL on a subscription Key: PROTON-674 URL: https://issues.apache.org/jira/browse/PROTON-674 Project:

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger->error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: 21_improve_perror_printing_windows_io.c.patch 21_improve_perror_printin

[jira] [Commented] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger->error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129889#comment-14129889 ] Dominic Evans commented on PROTON-571: -- Additional patchset to fix Windows socket err

  1   2   >