[jira] [Created] (PROTON-2854) Make it easier to build with AFL fuzzer manually
Andrew Stitcher created PROTON-2854: --- Summary: Make it easier to build with AFL fuzzer manually Key: PROTON-2854 URL: https://issues.apache.org/jira/browse/PROTON-2854 Project: Qpid Proton Issue Type: Improvement Reporter: Andrew Stitcher The fuzzing tests have code to build with libFuzzingEngine but that makes it harder to build with AFL. We introduce a setting to select the fuzzer in use. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2853) Undefined behaviour found by fuzzing transfer frame
Andrew Stitcher created PROTON-2853: --- Summary: Undefined behaviour found by fuzzing transfer frame Key: PROTON-2853 URL: https://issues.apache.org/jira/browse/PROTON-2853 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fuzzing found that if an initial transfer frame has no (or an invalid) delivery id no error is raised but in debug mode an assertion would be tripped. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2848) [python] Add py.typed marker to officially support typing and be compliant with PEP 561
[ https://issues.apache.org/jira/browse/PROTON-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2848. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [python] Add py.typed marker to officially support typing and be compliant > with PEP 561 > --- > > Key: PROTON-2848 > URL: https://issues.apache.org/jira/browse/PROTON-2848 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Patrick Taibel >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.40.0 > > > As far as I can tell the python binding is properly typed. In order to allow > using tools like mypy it is required to have a {{py.typed}} file packaged > (see PEP 561). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2848) [python] Add py.typed marker to officially support typing and be compliant with PEP 561
[ https://issues.apache.org/jira/browse/PROTON-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2848: --- Assignee: Andrew Stitcher > [python] Add py.typed marker to officially support typing and be compliant > with PEP 561 > --- > > Key: PROTON-2848 > URL: https://issues.apache.org/jira/browse/PROTON-2848 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Patrick Taibel >Assignee: Andrew Stitcher >Priority: Minor > > As far as I can tell the python binding is properly typed. In order to allow > using tools like mypy it is required to have a {{py.typed}} file packaged > (see PEP 561). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2844) Modernize python code
Andrew Stitcher created PROTON-2844: --- Summary: Modernize python code Key: PROTON-2844 URL: https://issues.apache.org/jira/browse/PROTON-2844 Project: Qpid Proton Issue Type: Improvement Components: proton-c, python-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher There are still some places in the python binding and tests that are not using the most recent idiomatic python or still check for version 2 python. These should be tidied up now we only need to support python 3.9 and later. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2842) Frame dump for custom descriptors is incorrect
[ https://issues.apache.org/jira/browse/PROTON-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2842. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Frame dump for custom descriptors is incorrect > -- > > Key: PROTON-2842 > URL: https://issues.apache.org/jira/browse/PROTON-2842 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.40.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2842) Frame dump for custom descriptors is incorrect
Andrew Stitcher created PROTON-2842: --- Summary: Frame dump for custom descriptors is incorrect Key: PROTON-2842 URL: https://issues.apache.org/jira/browse/PROTON-2842 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2839) New Proton API to more efficiently create/query compound AMQP types
Andrew Stitcher created PROTON-2839: --- Summary: New Proton API to more efficiently create/query compound AMQP types Key: PROTON-2839 URL: https://issues.apache.org/jira/browse/PROTON-2839 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2838) Remove all operations using the pn_data_t structure from the frame decode path
Andrew Stitcher created PROTON-2838: --- Summary: Remove all operations using the pn_data_t structure from the frame decode path Key: PROTON-2838 URL: https://issues.apache.org/jira/browse/PROTON-2838 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher The pn_data_t structure is relatively inefficient and consumes quite a lot of memory. There are a number of places that it is used in decoding incoming frames whether or not that part of the frame is ever required by the application via the Proton API. We can avoid decoding the relevant protocol fields until the API requests them by just storing the raw protocol bytes and only creating the equivalent pn_data_t if it is requested by the API. This will also form the groundwork for a new API that allows us to creat and query these fields more efficiently using a new API. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2810) C++ compile standard needs to be advanced to c++14 or later
[ https://issues.apache.org/jira/browse/PROTON-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2810. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > C++ compile standard needs to be advanced to c++14 or later > --- > > Key: PROTON-2810 > URL: https://issues.apache.org/jira/browse/PROTON-2810 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, examples >Reporter: Kim van der Riet >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > The use of opentelemetry-cpp API in qpid-proton is forcing the C++ compile > standard to be c++14 or later. The support for c++11 (which qpid-proton is > currently using) in opentelemetry-cpp was removed in v 1.12.0 (we are > currently at version 1.14.2), and the use of its APIs is causing compile > errors. > Consideration should be given to moving the compiler C++ standard to 14, 17 > or even 20. > I have tested the compile using c++17, and this does not create any compile > errors, and solves the opentelemetry-cpp API error too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2831) Mistaken use of logical-or operator instead of bitwise-or operator
[ https://issues.apache.org/jira/browse/PROTON-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2831. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Mistaken use of logical-or operator instead of bitwise-or operator > -- > > Key: PROTON-2831 > URL: https://issues.apache.org/jira/browse/PROTON-2831 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This was picked up by tighter warnings in the latest Visual C++ compiler. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2835) [Win TLS] Incorrect certificate checking - not checking time validity
[ https://issues.apache.org/jira/browse/PROTON-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2835. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [Win TLS] Incorrect certificate checking - not checking time validity > - > > Key: PROTON-2835 > URL: https://issues.apache.org/jira/browse/PROTON-2835 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > Due to PROTON-2831 the certificate check flags to > {{CertGetIssuerCertificateFromStore}} were incorrect and effectively set to 1 > which is just the flag for "Check certificate signature". Additionally an > extra seemingly invalid flag was set - {{CERT_STORE_NO_ISSUER_FLAG}}. It > seems that this is purely an _output_ flag and is invalid to set on input. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2835) [Win TLS] Incorrect certificate checking - not checking time validity
Andrew Stitcher created PROTON-2835: --- Summary: [Win TLS] Incorrect certificate checking - not checking time validity Key: PROTON-2835 URL: https://issues.apache.org/jira/browse/PROTON-2835 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher Due to PROTON-2831 the certificate check flags to {{CertGetIssuerCertificateFromStore}} were incorrect and effectively set to 1 which is just the flag for "Check certificate signature". Additionally an extra seemingly invalid flag was set - {{CERT_STORE_NO_ISSUER_FLAG}}. It seems that this is purely an _output_ flag and is invalid to set on input. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2831) Mistaken use of logical-or operator instead of bitwise-or operator
Andrew Stitcher created PROTON-2831: --- Summary: Mistaken use of logical-or operator instead of bitwise-or operator Key: PROTON-2831 URL: https://issues.apache.org/jira/browse/PROTON-2831 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher This was picked up by tighter warnings in the latest Visual C++ compiler. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2824) C example broker doesn't respond well if the client tries to use transactions
[ https://issues.apache.org/jira/browse/PROTON-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2824. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > C example broker doesn't respond well if the client tries to use transactions > - > > Key: PROTON-2824 > URL: https://issues.apache.org/jira/browse/PROTON-2824 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > If the broker doesn't support transactions it should close the link to the > transaction coordinator when the attach is attempted. Currently it just > attaches the link. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2825) C++ binding treats transaction coordinator termini incorrectly
[ https://issues.apache.org/jira/browse/PROTON-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2825. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > C++ binding treats transaction coordinator termini incorrectly > -- > > Key: PROTON-2825 > URL: https://issues.apache.org/jira/browse/PROTON-2825 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > The C++ binding has no abstraction to represent a transaction coordinator > terminus but when it receives an attach with a target terminus which is a > transaction coordinator it just opens the link. > However because there is no correct abstraction for the transaction > coordinator terminus the server end of the link cannot respond correctly to > transaction messages being sent over this link. It doesn't even know that it > is not just a regular target terminus. > As an aside, even if there was some way of knowing about the transaction > coordinator there isn't any way in the C++ bindings to construct the correct > disposition messages necessary to respond to the transaction control messages. > Currently the binding should just reject the initial attempt to attach the > transaction controller terminus. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2825) C++ binding treats transaction coordinator termini incorrectly
Andrew Stitcher created PROTON-2825: --- Summary: C++ binding treats transaction coordinator termini incorrectly Key: PROTON-2825 URL: https://issues.apache.org/jira/browse/PROTON-2825 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher The C++ binding has no abstraction to represent a transaction coordinator terminus but when it receives an attach with a target terminus which is a transaction coordinator it just opens the link. However because there is no correct abstraction for the transaction coordinator terminus the server end of the link cannot respond correctly to transaction messages being sent over this link. It doesn't even know that it is not just a regular target terminus. As an aside, even if there was some way of knowing about the transaction coordinator there isn't any way in the C++ bindings to construct the correct disposition messages necessary to respond to the transaction control messages. Currently the binding should just reject the initial attempt to attach the transaction controller terminus. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2824) C example broker doesn't respond well if the client tries to use transactions
[ https://issues.apache.org/jira/browse/PROTON-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2824: Description: If the broker doesn't support transactions it should close the link to the transaction coordinator when the attach is attempted. Currently it just attaches the link. > C example broker doesn't respond well if the client tries to use transactions > - > > Key: PROTON-2824 > URL: https://issues.apache.org/jira/browse/PROTON-2824 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > If the broker doesn't support transactions it should close the link to the > transaction coordinator when the attach is attempted. Currently it just > attaches the link. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2824) C example broker doesn't respond well if the client tries to use transactions
Andrew Stitcher created PROTON-2824: --- Summary: C example broker doesn't respond well if the client tries to use transactions Key: PROTON-2824 URL: https://issues.apache.org/jira/browse/PROTON-2824 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2822) Build fails without building the proactor library
[ https://issues.apache.org/jira/browse/PROTON-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2822. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Build fails without building the proactor library > - > > Key: PROTON-2822 > URL: https://issues.apache.org/jira/browse/PROTON-2822 > Project: Qpid Proton > Issue Type: Bug > Components: build >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.40.0 > > > The build should be able to build the core library and test it without > building the proactor or other libraries - this seems to have bit rotted. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2822) Build fails without building the proactor library
Andrew Stitcher created PROTON-2822: --- Summary: Build fails without building the proactor library Key: PROTON-2822 URL: https://issues.apache.org/jira/browse/PROTON-2822 Project: Qpid Proton Issue Type: Bug Components: build Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher The build should be able to build the core library and test it without building the proactor or other libraries - this seems to have bit rotted. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2819) Fuzzer build failure, Python 3.9 could not be located in CMake
[ https://issues.apache.org/jira/browse/PROTON-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843092#comment-17843092 ] Andrew Stitcher commented on PROTON-2819: - Would it make sense to use an even later version of python than 3.9? Perhaps 3.12 so that the change would have greater longevity? > Fuzzer build failure, Python 3.9 could not be located in CMake > -- > > Key: PROTON-2819 > URL: https://issues.apache.org/jira/browse/PROTON-2819 > Project: Qpid Proton > Issue Type: Bug >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > {noformat} > Step #3 - "compile-afl-address-x86_64": + cmake .. -DCMAKE_BUILD_TYPE=Release > -DENABLE_LINKTIME_OPTIMIZATION=OFF -DBUILD_STATIC_LIBS=ON > -DENABLE_FUZZ_TESTING=ON -DFUZZ_REGRESSION_TESTS=OFF > Step #3 - "compile-afl-address-x86_64": -- The C compiler identification is > Clang 15.0.0 > Step #3 - "compile-afl-address-x86_64": -- Detecting C compiler ABI info > Step #3 - "compile-afl-address-x86_64": -- Detecting C compiler ABI info - > done > Step #3 - "compile-afl-address-x86_64": -- Check for working C compiler: > /src/aflplusplus/afl-clang-fast - skipped > Step #3 - "compile-afl-address-x86_64": -- Detecting C compile features > Step #3 - "compile-afl-address-x86_64": -- Detecting C compile features - done > Step #3 - "compile-afl-address-x86_64": -- Found OpenSSL: > /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.1.1f") > Step #3 - "compile-afl-address-x86_64": -- Performing Test > CMAKE_HAVE_LIBC_PTHREAD > Step #3 - "compile-afl-address-x86_64": -- Performing Test > CMAKE_HAVE_LIBC_PTHREAD - Success > Step #3 - "compile-afl-address-x86_64": -- Found Threads: TRUE > Step #3 - "compile-afl-address-x86_64": -- Could NOT find SWIG (missing: > SWIG_EXECUTABLE SWIG_DIR) > Step #3 - "compile-afl-address-x86_64": -- Could NOT find PkgConfig (missing: > PKG_CONFIG_EXECUTABLE) > Step #3 - "compile-afl-address-x86_64": -- Could NOT find CyrusSASL (missing: > CyrusSASL_LIBRARY CyrusSASL_INCLUDE_DIR) > Step #3 - "compile-afl-address-x86_64": [31mCMake Error at > /usr/local/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:230 > (message): > Step #3 - "compile-afl-address-x86_64": Could NOT find Python: Found > unsuitable version "3.8.3", but required is at > Step #3 - "compile-afl-address-x86_64": least "3.9" (found > /usr/local/bin/python3, found components: Interpreter > Step #3 - "compile-afl-address-x86_64": Development Development.Module > Development.Embed) > Step #3 - "compile-afl-address-x86_64": Call Stack (most recent call first): > Step #3 - "compile-afl-address-x86_64": > /usr/local/share/cmake-3.24/Modules/FindPackageHandleStandardArgs.cmake:592 > (_FPHSA_FAILURE_MESSAGE) > Step #3 - "compile-afl-address-x86_64": > /usr/local/share/cmake-3.24/Modules/FindPython/Support.cmake:3203 > (find_package_handle_standard_args) > Step #3 - "compile-afl-address-x86_64": > /usr/local/share/cmake-3.24/Modules/FindPython.cmake:519 (include) > Step #3 - "compile-afl-address-x86_64": CMakeLists.txt:45 (find_package) > {noformat} > https://oss-fuzz-build-logs.storage.googleapis.com/log-fd296220-df33-4d54-9538-a238afa45410.txt -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2820) [Ruby] Test failure when using swig 4.2
[ https://issues.apache.org/jira/browse/PROTON-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2820. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [Ruby] Test failure when using swig 4.2 > --- > > Key: PROTON-2820 > URL: https://issues.apache.org/jira/browse/PROTON-2820 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > Thid issue has newly appeared when building using Fedora 40, for example: > > {noformat} > 32: 1) Error: > 32: RawDriverTest#test_idle: > 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer > -3824857462615749666 > 32: in SWIG method 'pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `fetch_instance' > 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' > 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in > `transport' > 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in > `initialize' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in > `test_idle' > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2820) [Ruby] Test failure when using swig 4.2
[ https://issues.apache.org/jira/browse/PROTON-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843090#comment-17843090 ] Andrew Stitcher commented on PROTON-2820: - This seems to solely due to upgrading Swig 4.1 to 4.2. {{pn_handle_t}} is treated as if it was {{uintptr_t}} under the swig 4.1 it seems that the conversion from a negative integer to a {{pn_handle_t}} is fine even though {{pn_handle_t}} is supposed to be unsigned. Under swig 4.2 this conversion triggers an error. > [Ruby] Test failure when using swig 4.2 > --- > > Key: PROTON-2820 > URL: https://issues.apache.org/jira/browse/PROTON-2820 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > Thid issue has newly appeared when building using Fedora 40, for example: > > {noformat} > 32: 1) Error: > 32: RawDriverTest#test_idle: > 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer > -3824857462615749666 > 32: in SWIG method 'pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `fetch_instance' > 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' > 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in > `transport' > 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in > `initialize' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in > `test_idle' > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2820) [Ruby] Test failure when using swig 4.2
[ https://issues.apache.org/jira/browse/PROTON-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2820: Description: Thid issue has newly appeared when building using Fedora 40, for example: {noformat} 32: 1) Error: 32: RawDriverTest#test_idle: 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer -3824857462615749666 32: in SWIG method 'pn_record_get' 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in `pn_record_get' 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in `fetch_instance' 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in `transport' 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in `initialize' 32: /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' 32: /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `test_idle' {noformat} was: For example {noformat} 32: 1) Error: 32: RawDriverTest#test_idle: 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer -3824857462615749666 32: in SWIG method 'pn_record_get' 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in `pn_record_get' 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in `fetch_instance' 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in `transport' 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in `initialize' 32: /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' 32: /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `test_idle' {noformat} > [Ruby] Test failure when using swig 4.2 > --- > > Key: PROTON-2820 > URL: https://issues.apache.org/jira/browse/PROTON-2820 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > Thid issue has newly appeared when building using Fedora 40, for example: > > {noformat} > 32: 1) Error: > 32: RawDriverTest#test_idle: > 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer > -3824857462615749666 > 32: in SWIG method 'pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `fetch_instance' > 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' > 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in > `transport' > 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in > `initialize' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in > `test_idle' > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2820) [Ruby] Test failure when using swig 4.2
[ https://issues.apache.org/jira/browse/PROTON-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2820: --- Assignee: Andrew Stitcher (was: Alan Conway) > [Ruby] Test failure when using swig 4.2 > --- > > Key: PROTON-2820 > URL: https://issues.apache.org/jira/browse/PROTON-2820 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > For example > > {noformat} > 32: 1) Error: > 32: RawDriverTest#test_idle: > 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer > -3824857462615749666 > 32: in SWIG method 'pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `pn_record_get' > 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in > `fetch_instance' > 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' > 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in > `transport' > 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in > `initialize' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' > 32: > /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in > `test_idle' > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2820) [Ruby] Test failure when using swig 4.2
Andrew Stitcher created PROTON-2820: --- Summary: [Ruby] Test failure when using swig 4.2 Key: PROTON-2820 URL: https://issues.apache.org/jira/browse/PROTON-2820 Project: Qpid Proton Issue Type: Bug Components: ruby-binding Reporter: Andrew Stitcher Assignee: Alan Conway For example {noformat} 32: 1) Error: 32: RawDriverTest#test_idle: 32: TypeError: Expected argument 1 of type pn_handle_t, but got Integer -3824857462615749666 32: in SWIG method 'pn_record_get' 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in `pn_record_get' 32: /home/andrew/Work/proton/src/ruby/lib/util/wrapper.rb:94:in `fetch_instance' 32: /home/andrew/Work/proton/src/ruby/lib/core/transport.rb:167:in `wrap' 32: /home/andrew/Work/proton/src/ruby/lib/core/connection_driver.rb:50:in `transport' 32: /home/andrew/Work/proton/src/ruby/tests/test_tools.rb:118:in `initialize' 32: /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `new' 32: /home/andrew/Work/proton/src/ruby/tests/test_connection_driver.rb:68:in `test_idle' {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2810) C++ compile standard needs to be advanced to c++14 or later
[ https://issues.apache.org/jira/browse/PROTON-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2810: --- Assignee: Andrew Stitcher > C++ compile standard needs to be advanced to c++14 or later > --- > > Key: PROTON-2810 > URL: https://issues.apache.org/jira/browse/PROTON-2810 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, examples >Reporter: Kim van der Riet >Assignee: Andrew Stitcher >Priority: Major > > The use of opentelemetry-cpp API in qpid-proton is forcing the C++ compile > standard to be c++14 or later. The support for c++11 (which qpid-proton is > currently using) in opentelemetry-cpp was removed in v 1.12.0 (we are > currently at version 1.14.2), and the use of its APIs is causing compile > errors. > Consideration should be given to moving the compiler C++ standard to 14, 17 > or even 20. > I have tested the compile using c++17, and this does not create any compile > errors, and solves the opentelemetry-cpp API error too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2817) [Python] Allow control of whether python build uses pip inside virtual environments
[ https://issues.apache.org/jira/browse/PROTON-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2817. - Resolution: Fixed > [Python] Allow control of whether python build uses pip inside virtual > environments > --- > > Key: PROTON-2817 > URL: https://issues.apache.org/jira/browse/PROTON-2817 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > For the purposes of distribution package building (and other repeatable, > reliable environments). We need to have a way to restrict the python build > from attemping to access the internet to download updated packages as part of > its build. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2816. - Resolution: Fixed > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2815) [Python] Use up to date tooling to produce python packages
[ https://issues.apache.org/jira/browse/PROTON-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2815. - Resolution: Fixed > [Python] Use up to date tooling to produce python packages > -- > > Key: PROTON-2815 > URL: https://issues.apache.org/jira/browse/PROTON-2815 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > Using setup.py as a python script to produce python packages/install packages > etc has been deprecated for a little while and will be going away from python > soon. > We should update our build to use a supported tool to build our packages. > The simplest approach would be to use the 'build' module with the setuptools > backend. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2817) [Python] Allow control of whether python build uses pip inside virtual environments
Andrew Stitcher created PROTON-2817: --- Summary: [Python] Allow control of whether python build uses pip inside virtual environments Key: PROTON-2817 URL: https://issues.apache.org/jira/browse/PROTON-2817 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.40.0 For the purposes of distribution package building (and other repeatable, reliable environments). We need to have a way to restrict the python build from attemping to access the internet to download updated packages as part of its build. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
Andrew Stitcher created PROTON-2816: --- Summary: The current python pkg build can only build a package with a bundled proton core Key: PROTON-2816 URL: https://issues.apache.org/jira/browse/PROTON-2816 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.38.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.40.0 This is an issue for 2 scenarios: - Producing python packages for distributions that should depend on the system installed proton core library - Debugging the C code (either library or adaptation layer code) when running from python. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2815) [Python] Use up to date tooling to produce python packages
Andrew Stitcher created PROTON-2815: --- Summary: [Python] Use up to date tooling to produce python packages Key: PROTON-2815 URL: https://issues.apache.org/jira/browse/PROTON-2815 Project: Qpid Proton Issue Type: Improvement Components: python-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Using setup.py as a python script to produce python packages/install packages etc has been deprecated for a little while and will be going away from python soon. We should update our build to use a supported tool to build our packages. The simplest approach would be to use the 'build' module with the setuptools backend. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2792) [cpp] Segmentation fault in container::impl::run_timer_jobs
[ https://issues.apache.org/jira/browse/PROTON-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2792. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [cpp] Segmentation fault in container::impl::run_timer_jobs > --- > > Key: PROTON-2792 > URL: https://issues.apache.org/jira/browse/PROTON-2792 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.38.0 >Reporter: Martin Zlomek >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > PROTON-2438 introduced a race condition in > [reading|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L545] > / > [writing|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L547] > {{is_active_}} in > [{{run_timer_jobs()}}|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L498] > while modifying it in > [{{schedule()}}|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L455] > or > [{{cancel()}}|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L473] > at the same time. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2792) [cpp] Segmentation fault in container::impl::run_timer_jobs
[ https://issues.apache.org/jira/browse/PROTON-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2792: --- Assignee: Andrew Stitcher > [cpp] Segmentation fault in container::impl::run_timer_jobs > --- > > Key: PROTON-2792 > URL: https://issues.apache.org/jira/browse/PROTON-2792 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.38.0 >Reporter: Martin Zlomek >Assignee: Andrew Stitcher >Priority: Major > > PROTON-2438 introduced a race condition in > [reading|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L545] > / > [writing|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L547] > {{is_active_}} in > [{{run_timer_jobs()}}|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L498] > while modifying it in > [{{schedule()}}|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L455] > or > [{{cancel()}}|https://github.com/DreamPearl/qpid-proton/blob/8142e3cecd9f668992e76a5448afc09fd7b1030a/cpp/src/proactor_container_impl.cpp#L473] > at the same time. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2644) Update various GH actions versions to resolve deprecation warnings
[ https://issues.apache.org/jira/browse/PROTON-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2644. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Update various GH actions versions to resolve deprecation warnings > -- > > Key: PROTON-2644 > URL: https://issues.apache.org/jira/browse/PROTON-2644 > Project: Qpid Proton > Issue Type: Task > Components: build >Affects Versions: proton-c-0.38.0 >Reporter: Jiri Daněk >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > Note that upgrading install-python to v4 breaks macOS build, as openssl is > then not found by cmake > https://github.com/gemmellr/qpid-proton/actions/runs/3368665379/jobs/5587466718 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2644) Update various GH actions versions to resolve deprecation warnings
[ https://issues.apache.org/jira/browse/PROTON-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2644: --- Assignee: Andrew Stitcher > Update various GH actions versions to resolve deprecation warnings > -- > > Key: PROTON-2644 > URL: https://issues.apache.org/jira/browse/PROTON-2644 > Project: Qpid Proton > Issue Type: Task > Components: build >Affects Versions: proton-c-0.38.0 >Reporter: Jiri Daněk >Assignee: Andrew Stitcher >Priority: Major > > Note that upgrading install-python to v4 breaks macOS build, as openssl is > then not found by cmake > https://github.com/gemmellr/qpid-proton/actions/runs/3368665379/jobs/5587466718 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2814) [Python] Python tests incompatible with python 3.12
[ https://issues.apache.org/jira/browse/PROTON-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2814. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [Python] Python tests incompatible with python 3.12 > --- > > Key: PROTON-2814 > URL: https://issues.apache.org/jira/browse/PROTON-2814 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > Python 3.12 removes {{cgi.escape()}} which is used by the python tests to > output Junit compatible failure information. > The use can be simply replaced with {{{}html.escape(){}}}. > [Thanks to [~jdanek] for finding this issue before we had a failure actually > trigger it!] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2813) [Python] Make the python code pep8 clean
[ https://issues.apache.org/jira/browse/PROTON-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2813. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [Python] Make the python code pep8 clean > > > Key: PROTON-2813 > URL: https://issues.apache.org/jira/browse/PROTON-2813 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > It's better if we only accept code that conforms to the minimal coding > standards that we actively check. In PROTON-2320 we started this for python, > but left significant parts of the source tree alone. > We should finish the job and ensure that al;l python code conforms to PEP8 > except where it can't. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2814) [Python] Python tests incompatible with python 3.12
Andrew Stitcher created PROTON-2814: --- Summary: [Python] Python tests incompatible with python 3.12 Key: PROTON-2814 URL: https://issues.apache.org/jira/browse/PROTON-2814 Project: Qpid Proton Issue Type: Bug Components: python-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher Python 3.12 removes {{cgi.escape()}} which is used by the python tests to output Junit compatible failure information. The use can be simply replaced with {{{}html.escape(){}}}. [Thanks to [~jdanek] for finding this issue before we had a failure actually trigger it!] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2322) Fix and remove ignores in flake8 configuration
[ https://issues.apache.org/jira/browse/PROTON-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2322. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Fix and remove ignores in flake8 configuration > -- > > Key: PROTON-2322 > URL: https://issues.apache.org/jira/browse/PROTON-2322 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: Jiri Daněk >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > Fixes with autopep8 in PROTON-2320 resolved most of flake8 warnings. There > are still warnings left that require human consideration and fixing. > For example, usage of bare {{except}} in the code. > This must be fixed manually. Fixed issues should then be removed from the > tox.ini flake8 ignore section. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2813) [Python] Make the python code pep8 clean
[ https://issues.apache.org/jira/browse/PROTON-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2813: --- Assignee: Andrew Stitcher > [Python] Make the python code pep8 clean > > > Key: PROTON-2813 > URL: https://issues.apache.org/jira/browse/PROTON-2813 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > It's better if we only accept code that conforms to the minimal coding > standards that we actively check. In PROTON-2320 we started this for python, > but left significant parts of the source tree alone. > We should finish the job and ensure that al;l python code conforms to PEP8 > except where it can't. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2813) [Python] Make the python code pep8 clean
[ https://issues.apache.org/jira/browse/PROTON-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2813: Description: It's better if we only accept code that conforms to the minimal coding standards that we actively check. In PROTON-2320 we started this for python, but left significant parts of the source tree alone. We should finish the job and ensure that al;l python code conforms to PEP8 except where it can't. was: It's better if we only accept code that conforms to the minimal coding standards that we actively check. In PROTON-2322 we started this for python, but left significant parts of the source tree alone. We should finish the job and ensure that al;l python code conforms to PEP8 except where it can't. > [Python] Make the python code pep8 clean > > > Key: PROTON-2813 > URL: https://issues.apache.org/jira/browse/PROTON-2813 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Andrew Stitcher >Priority: Major > > It's better if we only accept code that conforms to the minimal coding > standards that we actively check. In PROTON-2320 we started this for python, > but left significant parts of the source tree alone. > We should finish the job and ensure that al;l python code conforms to PEP8 > except where it can't. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2322) Fix and remove ignores in flake8 configuration
[ https://issues.apache.org/jira/browse/PROTON-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2322: --- Assignee: Andrew Stitcher > Fix and remove ignores in flake8 configuration > -- > > Key: PROTON-2322 > URL: https://issues.apache.org/jira/browse/PROTON-2322 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: Jiri Daněk >Assignee: Andrew Stitcher >Priority: Major > > Fixes with autopep8 in PROTON-2320 resolved most of flake8 warnings. There > are still warnings left that require human consideration and fixing. > For example, usage of bare {{except}} in the code. > This must be fixed manually. Fixed issues should then be removed from the > tox.ini flake8 ignore section. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2813) [Python] Make the python code pep8 clean
Andrew Stitcher created PROTON-2813: --- Summary: [Python] Make the python code pep8 clean Key: PROTON-2813 URL: https://issues.apache.org/jira/browse/PROTON-2813 Project: Qpid Proton Issue Type: Improvement Components: python-binding Reporter: Andrew Stitcher It's better if we only accept code that conforms to the minimal coding standards that we actively check. In PROTON-2322 we started this for python, but left significant parts of the source tree alone. We should finish the job and ensure that al;l python code conforms to PEP8 except where it can't. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2765) [go] Go compilation fails with go 1.21
[ https://issues.apache.org/jira/browse/PROTON-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2765. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [go] Go compilation fails with go 1.21 > -- > > Key: PROTON-2765 > URL: https://issues.apache.org/jira/browse/PROTON-2765 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > Error message is: > {noformat} > # github.com/apache/qpid-proton/go/pkg/amqp > Error: go/pkg/amqp/types.go:32:9: cannot define new methods on non-local type > C.pn_type_t > Error: go/pkg/amqp/unmarshal.go:729:13: cannot define new methods on > non-local type *C.pn_data_t > Error: go/pkg/amqp/unmarshal.go:730:13: cannot define new methods on > non-local type *C.pn_data_t > Error: go/pkg/amqp/unmarshal.go:731:13: cannot define new methods on > non-local type *C.pn_data_t > make[2]: *** [go/CMakeFiles/go-build] Error 1 > make[1]: *** [go/CMakeFiles/go-build.dir/all] Error 2 > make: *** [all] Error 2 > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2765) [go] Go compilation fails with go 1.21
Andrew Stitcher created PROTON-2765: --- Summary: [go] Go compilation fails with go 1.21 Key: PROTON-2765 URL: https://issues.apache.org/jira/browse/PROTON-2765 Project: Qpid Proton Issue Type: Bug Components: go-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher Error message is: {noformat} # github.com/apache/qpid-proton/go/pkg/amqp Error: go/pkg/amqp/types.go:32:9: cannot define new methods on non-local type C.pn_type_t Error: go/pkg/amqp/unmarshal.go:729:13: cannot define new methods on non-local type *C.pn_data_t Error: go/pkg/amqp/unmarshal.go:730:13: cannot define new methods on non-local type *C.pn_data_t Error: go/pkg/amqp/unmarshal.go:731:13: cannot define new methods on non-local type *C.pn_data_t make[2]: *** [go/CMakeFiles/go-build] Error 1 make[1]: *** [go/CMakeFiles/go-build.dir/all] Error 2 make: *** [all] Error 2 {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2762) [C++, tracing] Binding does not compile with opentracing
[ https://issues.apache.org/jira/browse/PROTON-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2762. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [C++, tracing] Binding does not compile with opentracing > > > Key: PROTON-2762 > URL: https://issues.apache.org/jira/browse/PROTON-2762 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > It seems that the opentracing compile of the C++ bindings was previously > dependent on a transitive header include that has gone away with a new > version of opentracing and now the compile fails because there is no > OPENTELEMETRY_SDK_VERSION #define. > We need to include -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2762) [C++, tracing] Binding does not compile with opentracing
Andrew Stitcher created PROTON-2762: --- Summary: [C++, tracing] Binding does not compile with opentracing Key: PROTON-2762 URL: https://issues.apache.org/jira/browse/PROTON-2762 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher It seems that the opentracing compile of the C++ bindings was previously dependent on a transitive header include that has gone away with a new version of opentracing and now the compile fails because there is no OPENTELEMETRY_SDK_VERSION #define. We need to include -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2760) Ruby Some unit tests fail as they use MiniTest which is no longer an alias for Minitest
[ https://issues.apache.org/jira/browse/PROTON-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2760: Fix Version/s: proton-c-0.40.0 > Ruby Some unit tests fail as they use MiniTest which is no longer an alias > for Minitest > --- > > Key: PROTON-2760 > URL: https://issues.apache.org/jira/browse/PROTON-2760 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding > Environment: Fedora rawhide (39) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > {noformat} > 29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in (required)>': uninitialized constant MiniTest (NameError) > 29: > 29: MiniTest::Test = MiniTest::Unit::TestCase > 29: > 29: Did you mean? Minitest > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2761) The ruby unittests give deprecation warnings
[ https://issues.apache.org/jira/browse/PROTON-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2761. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > The ruby unittests give deprecation warnings > - > > Key: PROTON-2761 > URL: https://issues.apache.org/jira/browse/PROTON-2761 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.40.0 > > > {noformat} > 40: # Running: > 40: > 40: The extended array type#test_0002_raises an error when the current object > is not a list = /opt/qpid-proton/ruby/lib/codec/data.rb:68: warning: und > efining the allocator of T_DATA class SWIG::TYPE_p_pn_data_t > 40: DEPRECATED: global use of must_raise from > /opt/qpid-proton/ruby/spec/array_spec.rb:43. Use _\{obj.method}.must_raise > instead. This will fail in Min > itest 6. > 40: 0.00 s = . > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2760) Ruby Some unit tests fail as they use MiniTest which is no longer an alias for Minitest
[ https://issues.apache.org/jira/browse/PROTON-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2760. - Resolution: Fixed > Ruby Some unit tests fail as they use MiniTest which is no longer an alias > for Minitest > --- > > Key: PROTON-2760 > URL: https://issues.apache.org/jira/browse/PROTON-2760 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding > Environment: Fedora rawhide (39) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > {noformat} > 29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in (required)>': uninitialized constant MiniTest (NameError) > 29: > 29: MiniTest::Test = MiniTest::Unit::TestCase > 29: > 29: Did you mean? Minitest > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2760) Ruby Some unit tests fail as they use MiniTest which is no longer an alias for Minitest
[ https://issues.apache.org/jira/browse/PROTON-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2760: Description: {noformat} 29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in ': uninitialized constant MiniTest (NameError) 29: 29: MiniTest::Test = MiniTest::Unit::TestCase 29: 29: Did you mean? Minitest {noformat} was: {{29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in ': uninitialized constant MiniTest (NameError)}} {{29: }} {{29: MiniTest::Test = MiniTest::Unit::TestCase}} {{29: }} {{29: Did you mean? Minitest}} > Ruby Some unit tests fail as they use MiniTest which is no longer an alias > for Minitest > --- > > Key: PROTON-2760 > URL: https://issues.apache.org/jira/browse/PROTON-2760 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding > Environment: Fedora rawhide (39) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > {noformat} > 29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in (required)>': uninitialized constant MiniTest (NameError) > 29: > 29: MiniTest::Test = MiniTest::Unit::TestCase > 29: > 29: Did you mean? Minitest > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2761) The ruby unittests give deprecation warnings
[ https://issues.apache.org/jira/browse/PROTON-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2761: Description: {noformat} 40: # Running: 40: 40: The extended array type#test_0002_raises an error when the current object is not a list = /opt/qpid-proton/ruby/lib/codec/data.rb:68: warning: und efining the allocator of T_DATA class SWIG::TYPE_p_pn_data_t 40: DEPRECATED: global use of must_raise from /opt/qpid-proton/ruby/spec/array_spec.rb:43. Use _\{obj.method}.must_raise instead. This will fail in Min itest 6. 40: 0.00 s = . {noformat} was: 40: # Running: 40: 40: The extended array type#test_0002_raises an error when the current object is not a list = /opt/qpid-proton/ruby/lib/codec/data.rb:68: warning: und efining the allocator of T_DATA class SWIG::TYPE_p_pn_data_t 40: DEPRECATED: global use of must_raise from /opt/qpid-proton/ruby/spec/array_spec.rb:43. Use _\{obj.method}.must_raise instead. This will fail in Min itest 6. 40: 0.00 s = . > The ruby unittests give deprecation warnings > - > > Key: PROTON-2761 > URL: https://issues.apache.org/jira/browse/PROTON-2761 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > > {noformat} > 40: # Running: > 40: > 40: The extended array type#test_0002_raises an error when the current object > is not a list = /opt/qpid-proton/ruby/lib/codec/data.rb:68: warning: und > efining the allocator of T_DATA class SWIG::TYPE_p_pn_data_t > 40: DEPRECATED: global use of must_raise from > /opt/qpid-proton/ruby/spec/array_spec.rb:43. Use _\{obj.method}.must_raise > instead. This will fail in Min > itest 6. > 40: 0.00 s = . > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2761) The ruby unittests give deprecation warnings
Andrew Stitcher created PROTON-2761: --- Summary: The ruby unittests give deprecation warnings Key: PROTON-2761 URL: https://issues.apache.org/jira/browse/PROTON-2761 Project: Qpid Proton Issue Type: Bug Components: ruby-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher 40: # Running: 40: 40: The extended array type#test_0002_raises an error when the current object is not a list = /opt/qpid-proton/ruby/lib/codec/data.rb:68: warning: und efining the allocator of T_DATA class SWIG::TYPE_p_pn_data_t 40: DEPRECATED: global use of must_raise from /opt/qpid-proton/ruby/spec/array_spec.rb:43. Use _\{obj.method}.must_raise instead. This will fail in Min itest 6. 40: 0.00 s = . -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2760) Ruby Some unit tests fail as they use MiniTest which is no longer an alias for Minitest
[ https://issues.apache.org/jira/browse/PROTON-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2760: Summary: Ruby Some unit tests fail as they use MiniTest which is no longer an alias for Minitest (was: Ruby Some unit tests fail due as they use MiniTest which is no longer an alias for Minitest) > Ruby Some unit tests fail as they use MiniTest which is no longer an alias > for Minitest > --- > > Key: PROTON-2760 > URL: https://issues.apache.org/jira/browse/PROTON-2760 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding > Environment: Fedora rawhide (39) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > {{29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in (required)>': uninitialized constant MiniTest (NameError)}} > {{29: }} > {{29: MiniTest::Test = MiniTest::Unit::TestCase}} > {{29: }} > {{29: Did you mean? Minitest}} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2760) Ruby Some unit tests fail due as they use MiniTest which is no longer an alias for Minitest
[ https://issues.apache.org/jira/browse/PROTON-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2760: Description: {{29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in ': uninitialized constant MiniTest (NameError)}} {{29: }} {{29: MiniTest::Test = MiniTest::Unit::TestCase}} {{29: }} {{29: Did you mean? Minitest}} was: {{29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in ': uninitialized constant MiniTest (NameError) 29: 29: MiniTest::Test = MiniTest::Unit::TestCase 29: 29: Did you mean? Minitest }} > Ruby Some unit tests fail due as they use MiniTest which is no longer an > alias for Minitest > --- > > Key: PROTON-2760 > URL: https://issues.apache.org/jira/browse/PROTON-2760 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding > Environment: Fedora rawhide (39) >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > {{29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in (required)>': uninitialized constant MiniTest (NameError)}} > {{29: }} > {{29: MiniTest::Test = MiniTest::Unit::TestCase}} > {{29: }} > {{29: Did you mean? Minitest}} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2760) Ruby Some unit tests fail due as they use MiniTest which is no longer an alias for Minitest
Andrew Stitcher created PROTON-2760: --- Summary: Ruby Some unit tests fail due as they use MiniTest which is no longer an alias for Minitest Key: PROTON-2760 URL: https://issues.apache.org/jira/browse/PROTON-2760 Project: Qpid Proton Issue Type: Bug Components: ruby-binding Environment: Fedora rawhide (39) Reporter: Andrew Stitcher Assignee: Andrew Stitcher {{29: /opt/qpid-proton/ruby/tests/test_tools.rb:28:in `rescue in ': uninitialized constant MiniTest (NameError) 29: 29: MiniTest::Test = MiniTest::Unit::TestCase 29: 29: Did you mean? Minitest }} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2756) [Python] There is no way to run python tests except by building a virtual environment
[ https://issues.apache.org/jira/browse/PROTON-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2756: Summary: [Python] There is no way to run python tests except by building a virtual environment (was: [Python] There is no way to ru npython tests except by building a virtual environment) > [Python] There is no way to run python tests except by building a virtual > environment > - > > Key: PROTON-2756 > URL: https://issues.apache.org/jira/browse/PROTON-2756 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is particularly annoying when building in environments where there is no > internet access. As pip will always try to connect to the internet by default. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2756) [Python] There is no way to ru npython tests except by building a virtual environment
[ https://issues.apache.org/jira/browse/PROTON-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2756. - Resolution: Fixed > [Python] There is no way to ru npython tests except by building a virtual > environment > - > > Key: PROTON-2756 > URL: https://issues.apache.org/jira/browse/PROTON-2756 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is particularly annoying when building in environments where there is no > internet access. As pip will always try to connect to the internet by default. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2756) [Python] There is no way to ru npython tests except by building a virtual environment
Andrew Stitcher created PROTON-2756: --- Summary: [Python] There is no way to ru npython tests except by building a virtual environment Key: PROTON-2756 URL: https://issues.apache.org/jira/browse/PROTON-2756 Project: Qpid Proton Issue Type: Improvement Components: python-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.40.0 This is particularly annoying when building in environments where there is no internet access. As pip will always try to connect to the internet by default. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2755) [Python] Make python code and binding work with python 3.12
[ https://issues.apache.org/jira/browse/PROTON-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2755. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > [Python] Make python code and binding work with python 3.12 > --- > > Key: PROTON-2755 > URL: https://issues.apache.org/jira/browse/PROTON-2755 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2755) [Python] Make python code and binding work with python 3.12
Andrew Stitcher created PROTON-2755: --- Summary: [Python] Make python code and binding work with python 3.12 Key: PROTON-2755 URL: https://issues.apache.org/jira/browse/PROTON-2755 Project: Qpid Proton Issue Type: Improvement Components: python-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2754) Python example broker supports ANONYMOUS-RELAY but doesn't offer the capability
[ https://issues.apache.org/jira/browse/PROTON-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2754. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Python example broker supports ANONYMOUS-RELAY but doesn't offer the > capability > --- > > Key: PROTON-2754 > URL: https://issues.apache.org/jira/browse/PROTON-2754 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is particularly annoying since the server example now checks that the > broker it's connected to does support the capability (As it needs it). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2754) Python example broker supports ANONYMOUS-RELAY but doesn't offer the capability
Andrew Stitcher created PROTON-2754: --- Summary: Python example broker supports ANONYMOUS-RELAY but doesn't offer the capability Key: PROTON-2754 URL: https://issues.apache.org/jira/browse/PROTON-2754 Project: Qpid Proton Issue Type: Bug Components: python-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher This is particularly annoying since the server example now checks that the broker it's connected to does support the capability (As it needs it). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1162) connection capabilities are not sent correctly by default
[ https://issues.apache.org/jira/browse/PROTON-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1162. - Fix Version/s: proton-c-0.39.0 (was: proton-c-future) Assignee: Andrew Stitcher Resolution: Fixed I'm not 100% sure when this was fixed (maybe 0.38) but as of 0.39 it is fixed. > connection capabilities are not sent correctly by default > - > > Key: PROTON-1162 > URL: https://issues.apache.org/jira/browse/PROTON-1162 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-0.12.0 >Reporter: Gordon Sim >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.39.0 > > > The offered- or desired- capabilities on a connection, they are sent out > incorrectly unless they are explicitly added as symbol or Array containing > symbols. > E.g. instead of > {noformat} > conn.offered_capabilities=["foo", "bar"] > {noformat} > you must use: > {noformat} > conn.offered_capabilities=Array(UNDESCRIBED, Data.SYMBOL, symbol("foo"), > symbol("bar")) > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2751) Reduce use of pn_buffer_t when not needed
[ https://issues.apache.org/jira/browse/PROTON-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2751. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Reduce use of pn_buffer_t when not needed > - > > Key: PROTON-2751 > URL: https://issues.apache.org/jira/browse/PROTON-2751 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > pn_buffer_t has complex logic to hold and manage a ring buffer. But is being > used just to manage a resizeable bytes buffer. And in most of those places > the buffer doesn't really nned to be resized either! > So it can be replaced in many places with much simpler code. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2753) Split util.h to separate the C++ safe parts out of the C99 but not C++ parts
[ https://issues.apache.org/jira/browse/PROTON-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2753. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Split util.h to separate the C++ safe parts out of the C99 but not C++ parts > > > Key: PROTON-2753 > URL: https://issues.apache.org/jira/browse/PROTON-2753 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2752) Use pn_string_t/pn_bytes_t instead of raw char*
[ https://issues.apache.org/jira/browse/PROTON-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2752. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > Use pn_string_t/pn_bytes_t instead of raw char* > --- > > Key: PROTON-2752 > URL: https://issues.apache.org/jira/browse/PROTON-2752 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > There are a few places where we hold a pn_string_t convert it to char* then > convert it to pn_bytes_t. We can "cut out the middleman"! and be more > efficient and have less code overall! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2753) Split util.h to separate the C++ safe parts out of the C99 but not C++ parts
Andrew Stitcher created PROTON-2753: --- Summary: Split util.h to separate the C++ safe parts out of the C99 but not C++ parts Key: PROTON-2753 URL: https://issues.apache.org/jira/browse/PROTON-2753 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2752) Use pn_string_t/pn_bytes_t instead of raw char*
Andrew Stitcher created PROTON-2752: --- Summary: Use pn_string_t/pn_bytes_t instead of raw char* Key: PROTON-2752 URL: https://issues.apache.org/jira/browse/PROTON-2752 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher There are a few places where we hold a pn_string_t convert it to char* then convert it to pn_bytes_t. We can "cut out the middleman"! and be more efficient and have less code overall! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2751) Reduce use of pn_buffer_t when not needed
Andrew Stitcher created PROTON-2751: --- Summary: Reduce use of pn_buffer_t when not needed Key: PROTON-2751 URL: https://issues.apache.org/jira/browse/PROTON-2751 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher pn_buffer_t has complex logic to hold and manage a ring buffer. But is being used just to manage a resizeable bytes buffer. And in most of those places the buffer doesn't really nned to be resized either! So it can be replaced in many places with much simpler code. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2746) pn_value_dump can access uninitialised memory
[ https://issues.apache.org/jira/browse/PROTON-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2746. - Fix Version/s: proton-c-0.40.0 Resolution: Fixed > pn_value_dump can access uninitialised memory > - > > Key: PROTON-2746 > URL: https://issues.apache.org/jira/browse/PROTON-2746 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > It's a pretty small edge case but if the size of a symbol is 0 then we will > currently try to read the first character anyway. If the symbol is at the > very end of the bytes being decoded then the byte read is not part of the > bytes being decoded. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2746) pn_value_dump can access uninitialised memory
Andrew Stitcher created PROTON-2746: --- Summary: pn_value_dump can access uninitialised memory Key: PROTON-2746 URL: https://issues.apache.org/jira/browse/PROTON-2746 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Andrew Stitcher It's a pretty small edge case but if the size of a symbol is 0 then we will currently try to read the first character anyway. If the symbol is at the very end of the bytes being decoded then the byte read is not part of the bytes being decoded. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2743) Logging raw frames only log outgoing frames not incoming frames
[ https://issues.apache.org/jira/browse/PROTON-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2743. - Resolution: Fixed > Logging raw frames only log outgoing frames not incoming frames > --- > > Key: PROTON-2743 > URL: https://issues.apache.org/jira/browse/PROTON-2743 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2743) Logging raw frames only log outgoing frames not incoming frames
Andrew Stitcher created PROTON-2743: --- Summary: Logging raw frames only log outgoing frames not incoming frames Key: PROTON-2743 URL: https://issues.apache.org/jira/browse/PROTON-2743 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.40.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2183) [cpp client] No messaging_handler callback for aborted messages
[ https://issues.apache.org/jira/browse/PROTON-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2183. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > [cpp client] No messaging_handler callback for aborted messages > --- > > Key: PROTON-2183 > URL: https://issues.apache.org/jira/browse/PROTON-2183 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.30.0 >Reporter: Charles E. Rolke >Assignee: Rakhi Kumari >Priority: Major > Fix For: proton-c-0.39.0 > > Attachments: PROTON-2183-send-receive-console.log > > > A cpp receiver throws "receiver read failure" when an aborted message is > received. > A client based on: > {{ class simple_recv : public proton::messaging_handler}} > does not get called at (on_transport_error, on_connection_error, > on_session_error, on_sender_error, on_receiver_error, on_error). The > exception is thrown back to main() and the client application has no way to > intercept it. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2707) Incomplete dependencies between Ubuntu -dev packages for Proton
[ https://issues.apache.org/jira/browse/PROTON-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730682#comment-17730682 ] Andrew Stitcher commented on PROTON-2707: - [~jdanek] Is this meant to be an issue raised against qpid-proton? We do not maintain any packages here so I don't see what we can do about an issue with ubuntu or debian or fedora packages. I'm assuming that this is a missing package dependency or a missing installed cmake config file in a package. If there is some way we can help dowstream packagers to make their job easier then we should definitely do that though. > Incomplete dependencies between Ubuntu -dev packages for Proton > --- > > Key: PROTON-2707 > URL: https://issues.apache.org/jira/browse/PROTON-2707 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c, release >Affects Versions: proton-c-0.37.0 >Reporter: Jiri Daněk >Priority: Major > > I wanted to use qpid-proton devel package when compiling qpid-cpp broker. > I installed libqpid-proton11-dev > {noformat} > Get:10 http://ppa.launchpad.net/qpid/testing/ubuntu focal/main amd64 > libqpid-proton11-dev amd64 0.37.0-1focal+qpid1 [72.0 kB] > {noformat} > and that also brought in, as a dependency > {noformat} > Get:4 http://ppa.launchpad.net/qpid/testing/ubuntu focal/main amd64 > libqpid-proton11 amd64 0.37.0-1focal+qpid1 [151 kB] > {noformat} > But then qpid-cpp broker build failed with > {noformat} > CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Proton/ProtonTargets.cmake:87 > (message): > The imported target "Proton::core" references the file > -- Configuring incomplete, errors occurred! > "/usr/lib/x86_64-linux-gnu/libqpid-proton-core.so.10.13.0" > but this file does not exist. Possible reasons include: > * The file was deleted, renamed, or moved to another location. > * An install or uninstall procedure did not complete successfully. > * The installation package was faulty and contained > "/usr/lib/x86_64-linux-gnu/cmake/Proton/ProtonTargets.cmake" > but not all the files it references. > Call Stack (most recent call first): > /usr/lib/x86_64-linux-gnu/cmake/Proton/ProtonConfig.cmake:61 (include) > CMakeModules/FindProton.cmake:24 (find_package) > {noformat} > https://github.com/jiridanek/qpid-cpp/actions/runs/4640812333/jobs/8213140438#step:12:101 > I had to manually also install libqpid-proton-core10-dev to have all the > necessary files. > Please add dependency between the dev packages. > Btw, looking at Ubuntu packages > https://packages.ubuntu.com/source/focal/qpid-proton I noticed that they take > them from Debian, and those packages are out-of-date (even more than I'd > expect) and they don't include ProtonConfig.cmake, and these other cmake > files in the -dev packages. > Also, there are no Ubuntu Jammy packages in the Qpid PPA yet, > https://launchpad.net/~qpid/+archive/ubuntu/testing/+packages -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2209) Link max-message-size has no effect
[ https://issues.apache.org/jira/browse/PROTON-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2209: Priority: Major (was: Critical) > Link max-message-size has no effect > --- > > Key: PROTON-2209 > URL: https://issues.apache.org/jira/browse/PROTON-2209 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.30.0 >Reporter: Francisco Moraes >Priority: Major > > According to AMQP specification, a link can set a max message size via > *max-message-size* property on the *attach* frame. This works correctly and I > can verify that the value is being sent to the AMQP Broker (qpid-cpp in my > case). But messages larger than this setting are still being received and > there is no link error generated with *amqp:link:message-size-exceeded* which > would be expected when a large message is received. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2712) [Python] Inconsistencies in binding type mappings
[ https://issues.apache.org/jira/browse/PROTON-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713603#comment-17713603 ] Andrew Stitcher commented on PROTON-2712: - Ah, thanks - I can confirm that the fixed version produces a better result for user_id using the cli-proton-python sender > [Python] Inconsistencies in binding type mappings > - > > Key: PROTON-2712 > URL: https://issues.apache.org/jira/browse/PROTON-2712 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > There were some inconsistencies and infelicities in the new cffi API bindings > type mappings between python and C types -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2712) [Python] Inconsistencies in binding type mappings
[ https://issues.apache.org/jira/browse/PROTON-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713316#comment-17713316 ] Andrew Stitcher commented on PROTON-2712: - [~jdanek] I'm confused: my change precisely changes the user_id property to return a python bytes opbject not a memoryview object. Are you sure you are using the fixed version of the code? > [Python] Inconsistencies in binding type mappings > - > > Key: PROTON-2712 > URL: https://issues.apache.org/jira/browse/PROTON-2712 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > There were some inconsistencies and infelicities in the new cffi API bindings > type mappings between python and C types -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2712) [Python] Inconsistencies in binding type mappings
[ https://issues.apache.org/jira/browse/PROTON-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2712. - Resolution: Fixed > [Python] Inconsistencies in binding type mappings > - > > Key: PROTON-2712 > URL: https://issues.apache.org/jira/browse/PROTON-2712 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > There were some inconsistencies and infelicities in the new cffi API bindings > type mappings between python and C types -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2712) [Python] Inconsistencies in binding type mappings
Andrew Stitcher created PROTON-2712: --- Summary: [Python] Inconsistencies in binding type mappings Key: PROTON-2712 URL: https://issues.apache.org/jira/browse/PROTON-2712 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.39.0 There were some inconsistencies and infelicities in the new cffi API bindings type mappings between python and C types -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2401. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.39.0 > > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2679) Parallel build of python bindings occasionally fails
[ https://issues.apache.org/jira/browse/PROTON-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2679. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > Parallel build of python bindings occasionally fails > > > Key: PROTON-2679 > URL: https://issues.apache.org/jira/browse/PROTON-2679 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.39.0 >Reporter: Ken Giusti >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > See skupper CI failure: > [https://github.com/skupperproject/skupper-router/actions/runs/4056555498/jobs/6981190135#step:17:234] > Appears to be trying to build the same file twice: > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_condition.py > proton/_condition.py > > [ 38%] Generating proton/_condition.py > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_condition.py > proton/_condition.py > > [ 39%] Generating proton/_data.py > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_data.py > proton/_data.py > > [ 40%] Generating proton/_data.py > > cd /__w/skupper-router/skupper-router/qpid-proton/build/python && > /usr/bin/cmake -E copy > /home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_data.py > proton/_data.py > > Error copying file > "/home/runner/work/skupper-router/skupper-router/qpid-proton/python/proton/_condition.py" > to "proton/_condition.py". > > gmake[2]: *** [python/CMakeFiles/pydist.dir/build.make:280: > python/proton/_condition.py] Error 1 > > gmake[2]: *** Deleting file 'python/proton/_condition.py' > > gmake[2]: *** Waiting for unfinished jobs > > gmake[1]: *** [CMakeFiles/Makefile2:572: python/CMakeFiles/pydist.dir/all] > Error 2 > > gmake[2]: Leaving directory > '/__w/skupper-router/skupper-router/qpid-proton/build' > > gmake[1]: *** Waiting for unfinished jobs -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2709) Settle delivered messages in the C sender example
[ https://issues.apache.org/jira/browse/PROTON-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2709. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > Settle delivered messages in the C sender example > - > > Key: PROTON-2709 > URL: https://issues.apache.org/jira/browse/PROTON-2709 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Although it's not needed in the example because the link is fairly short > lived and so doesn't create excessive memory use, the sender should settle > the delivery when the message is accepted so as to free all memory resources > associated with it. This is necessary for a long lived sender and so the > example should show this. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2709) Settle delivered messages in the C sender example
Andrew Stitcher created PROTON-2709: --- Summary: Settle delivered messages in the C sender example Key: PROTON-2709 URL: https://issues.apache.org/jira/browse/PROTON-2709 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher Although it's not needed in the example because the link is fairly short lived and so doesn't create excessive memory use, the sender should settle the delivery when the message is accepted so as to free all memory resources associated with it. This is necessary for a long lived sender and so the example should show this. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2708) New proactor APIs to query event batch for subject
Andrew Stitcher created PROTON-2708: --- Summary: New proactor APIs to query event batch for subject Key: PROTON-2708 URL: https://issues.apache.org/jira/browse/PROTON-2708 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Andrew Stitcher Assignee: Andrew Stitcher The object that a proactor event batch refers can't change during the processing of the batch so you shouldn't need to extract the object from every individual event of the batch, This change introduces an API for each of the possible subjects of an event batch: {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}}, {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2401) on_link_closed is not called when remote detaches link and locally link is also closed.
[ https://issues.apache.org/jira/browse/PROTON-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-2401: --- Assignee: Andrew Stitcher > on_link_closed is not called when remote detaches link and locally link is > also closed. > --- > > Key: PROTON-2401 > URL: https://issues.apache.org/jira/browse/PROTON-2401 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.34.0 >Reporter: NS-SlaFleur >Assignee: Andrew Stitcher >Priority: Minor > > The on_link_closed for the MessagingHandler is not called when the link is > first detached by the remote and then locally. This is due to a missing > on_link_local_close in the EndpointStateHandler in _handlers.py. > > Pull Request: https://github.com/apache/qpid-proton/pull/323 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2706) [Python] Allow setting the container id for containers/connections
Andrew Stitcher created PROTON-2706: --- Summary: [Python] Allow setting the container id for containers/connections Key: PROTON-2706 URL: https://issues.apache.org/jira/browse/PROTON-2706 Project: Qpid Proton Issue Type: Improvement Reporter: Andrew Stitcher Assignee: Andrew Stitcher This is an improvement suggested by [~jmennius] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2704) [Python] The examples test hangs
Andrew Stitcher created PROTON-2704: --- Summary: [Python] The examples test hangs Key: PROTON-2704 URL: https://issues.apache.org/jira/browse/PROTON-2704 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.39.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.39.0 Running the python examples via the unittest in the examples directory hangs at the various sync client tests. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2701) [Python] Make python build respect BUILD_TESTING
[ https://issues.apache.org/jira/browse/PROTON-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2701. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > [Python] Make python build respect BUILD_TESTING > > > Key: PROTON-2701 > URL: https://issues.apache.org/jira/browse/PROTON-2701 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2701) [Python] Make python build respect BUILD_TESTING
Andrew Stitcher created PROTON-2701: --- Summary: [Python] Make python build respect BUILD_TESTING Key: PROTON-2701 URL: https://issues.apache.org/jira/browse/PROTON-2701 Project: Qpid Proton Issue Type: Bug Components: python-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2700) Raw connection API: Remove ambiguous use of READ/WRITTEN events
[ https://issues.apache.org/jira/browse/PROTON-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2700. - Fix Version/s: proton-c-0.39.0 Resolution: Done > Raw connection API: Remove ambiguous use of READ/WRITTEN events > --- > > Key: PROTON-2700 > URL: https://issues.apache.org/jira/browse/PROTON-2700 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > This is the completion of PROTON-2339: > We're now finally removing the uses of thesae events to signal to the > application to take back its buffers as there is an unambiguous event > (DRAIN_BUFFERS) for this purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2700) Raw connection API: Remove ambiguous use of READ/WRITTEN events
Andrew Stitcher created PROTON-2700: --- Summary: Raw connection API: Remove ambiguous use of READ/WRITTEN events Key: PROTON-2700 URL: https://issues.apache.org/jira/browse/PROTON-2700 Project: Qpid Proton Issue Type: Improvement Reporter: Andrew Stitcher Assignee: Andrew Stitcher This is the completion of PROTON-2339: We'ew now finally removing the uses of thesae events to signal to the application to take back its buffers as there is an unambiguous event (DRAIN_BUFFERS) for this purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2700) Raw connection API: Remove ambiguous use of READ/WRITTEN events
[ https://issues.apache.org/jira/browse/PROTON-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated PROTON-2700: Description: This is the completion of PROTON-2339: We're now finally removing the uses of thesae events to signal to the application to take back its buffers as there is an unambiguous event (DRAIN_BUFFERS) for this purpose. was: This is the completion of PROTON-2339: We'ew now finally removing the uses of thesae events to signal to the application to take back its buffers as there is an unambiguous event (DRAIN_BUFFERS) for this purpose. > Raw connection API: Remove ambiguous use of READ/WRITTEN events > --- > > Key: PROTON-2700 > URL: https://issues.apache.org/jira/browse/PROTON-2700 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > > This is the completion of PROTON-2339: > We're now finally removing the uses of thesae events to signal to the > application to take back its buffers as there is an unambiguous event > (DRAIN_BUFFERS) for this purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2690) [Python] The desired and offered capabilities field in open performative should be symbol array or symbol
Andrew Stitcher created PROTON-2690: --- Summary: [Python] The desired and offered capabilities field in open performative should be symbol array or symbol Key: PROTON-2690 URL: https://issues.apache.org/jira/browse/PROTON-2690 Project: Qpid Proton Issue Type: Bug Components: python-binding Reporter: Andrew Stitcher Assignee: Andrew Stitcher Currently if you pass a list (or a symbol list) to connection.open the performative that goes on the wire contains a list. The AMQP standard requires that the wire contains a symbol array or a single symbol. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2684) CFFI related TypeError: '%x format: an integer is required, not _cffi_backend._CDataBase'
[ https://issues.apache.org/jira/browse/PROTON-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2684. - Fix Version/s: proton-c-0.39.0 Resolution: Fixed > CFFI related TypeError: '%x format: an integer is required, not > _cffi_backend._CDataBase' > -- > > Key: PROTON-2684 > URL: https://issues.apache.org/jira/browse/PROTON-2684 > Project: Qpid Proton > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.39.0 > > > Hit in skupper-router CI test: > > > {code:java} > 36: self = object at 0x7fc9b9d5d550> > 36: event = <[TypeError('%x format: an integer is required, not > _cffi_backend._CDataBase') raised in repr()] Event object at 0x7fc9b9d76a90> > {code} > > > [https://github.com/skupperproject/skupper-router/actions/runs/4176741670/jobs/7233430902#step:30:847] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2678) Use Python Limited API and create universal wheel when building Qpid Proton Python client
[ https://issues.apache.org/jira/browse/PROTON-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2678. - Resolution: Fixed > Use Python Limited API and create universal wheel when building Qpid Proton > Python client > - > > Key: PROTON-2678 > URL: https://issues.apache.org/jira/browse/PROTON-2678 > Project: Qpid Proton > Issue Type: New Feature >Affects Versions: proton-c-0.39.0 >Reporter: Jiri Daněk >Assignee: Andrew Stitcher >Priority: Major > > Currently, the build produces Python-version-specific wheels > {noformat} > creating 'dist/python_qpid_proton-0.39.0.dev0-cp311-cp311-linux_x86_64 > {noformat} > Python is able to create universal wheels that can be installed on any > (reasonably new) Python version. See > #. https://peps.python.org/pep-0425/#overview > {quote}The CPython stable ABI is abi3 as in the shared library suffix.{quote} > #. > https://docs.python.org/3/c-api/stable.html#stable-application-binary-interface > #. https://docs.python.org/3/c-api/stable.html#c.Py_LIMITED_API > {quote}Define Py_LIMITED_API to the value of PY_VERSION_HEX corresponding to > the lowest Python version your extension supports. The extension will work > without recompilation with all Python 3 releases from the specified one > onward, and can use Limited API introduced up to that version.{quote} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org