By all means take some time to investigate, and we can ultimately
decide how to proceed based on what you find. If it turns out this
isnt a regression then it doesnt necessarily immediately seem like a
blocker either. We will do more releases, and it's essentially the
same amount of work for me to
+1
- verified signature and sha512 checksum
- built C and Python bindings on fedora 40 - Debug and RelWithDebInfo
- ctest passes (with caveat)
- ran against skupper-router CI - no failures
Caveat: the proton python-pep8-test fails for me when I run ctest. However
python-pep8-test fails for me wit
I've spent a bit of time looking at this and I think this is the result of
the new provider code in OpenSSL. It is still quite new, so very likely has
some issues like this.
So:
* I don't think it's a regression in proton
* The leak is tiny (only 32 bytes) over a full program run.
* Arguably it's
On 11/20/24 13:12, Robbie Gemmell wrote:
Hi folks,
I have put together a first spin for a Qpid Proton 0.40.0 release,
please give it a test out and vote accordingly.
The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.40.0-rc1/
The JIRAs assigned are:
https://is
+1
* Built and tested on FreeBSD14 with valgrind (AMD64 in a VM)
- No build/test errors
- C/C++/Python only
* Built and tested on Raspberry Pi 5 with valgrind (PiOS based on
debian 12.8)
- No build/test errors
- C/C++/Python/Ruby
* Built and tested on Fedora 41 with valgrind (x86_64)
- No bui
It doesnt dynamically prioritise based on expiration, but it does have
a 'sorted queue' that can dynamically sort messages on the queue based
on a string based property in the message that you could perhaps
leverage to that end.
On Fri, 22 Nov 2024 at 06:02, Vinita Meka wrote:
>
> Hi Qpid Users,
