In case you missed it I ported the coverage work done on proton to dispatch:
https://github.com/apache/qpid-dispatch/commit/802e4aa97f159c8464e9f21eabf11453c2688399
We can now check the coverage of our dispatch CI tests. This is a
useful tool when creating new unit tests (or updating the existin
As a fix to https://issues.apache.org/jira/browse/DISPATCH-894 , Qpid
Dispatch is now using Python's unittest2 (instead of unittest) to run unit
tests.
https://pypi.python.org/pypi/unittest2
"unittest2 is a backport of the new features added to the unittest testing
framework in Python 2.7 and on
Thank you Chris,
Unfortunately, what happens here is still not completely clear to me.
When I look at the binary data being sent (using PN_TRACE_FRM=1), I notice that
the b" never appears in the message being sent (not with C++ and not with
python), and that the body data itself is identical wha
Hi Olivier,
The 'b' prefix in this case is part of the automatic character encoding of
the language in use, indicating that the string is a "bytes" object rather
than a Unicode string which is the default expectation of the C++. Have a
browse of the relevant character encoding documentation for th
Hi all,
When I send messages to a queue using the java or python APIs, the message body
I receive on the other side (C++ binding) is preceded by b" and appended with ".
When I send the same message with the C++ API, I do not have this behaviour.
Example:
[C++] sender.send( proton::message("[ME
+1
fedora27, self tests, manual check of ruby and go examples.
On Thu, Dec 21, 2017 at 10:18 AM, Chuck Rolke wrote:
> +1
>
> on Fedora 27
> * Verified checksum
> * ran selftests [1]
> * linked with qpid-dispatch master
> * ran qpid-dispath selftests
>
> [1] On first go self qpid-proton test fai
+1
on Fedora 27
* Verified checksum
* ran selftests [1]
* linked with qpid-dispatch master
* ran qpid-dispath selftests
[1] On first go self qpid-proton test failed. The fail on qpid-proton master,
too.
Had to upgrade valgrind to 3.13.0-12 then they pass in 0.19.0-rc2 and master.
- Origina
There are two levels of authentication that can happen.
* TLS Handshake
For simple TLS the broker must present a certificate that is signed by a
certificate authority (CA) that the client trusts.
* TLS Handshake with Client Certificate Request
The broker must always send a certificate to the c
I need some basic help to understand better. I have two questions:
1) In order to make ssl connection, is it necessary to configure ssl
certificate and private key within the code. Wouldn't just changing the port
to 5671, having username and password, and adding amqps work?
2) I implemented this
