Re: [VOTE] Release Qpid Proton 0.11.0
On 11/11/2015 07:53 AM, Justin Ross wrote: > The artifacts proposed for release are here: > > https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-rc2/ > > Please indicate your vote below. If you favor releasing the 0.11.0 RC 2 > bits as 0.11.0 GA, vote +1. If you have reason to think RC 2 is not ready > for release, vote -1. > > Thanks! > Justin > +1 Tested ActiveMQ using the artifacts in staged maven repo Tested Qpid JMS using the staging repo Built from source and ran the tests, all passed Validated signature and sums Checked license an notice files -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
[jira] [Created] (PROTON-1045) Use of callbacks to handle accepted endpoints violates design goals.
Alan Conway created PROTON-1045: --- Summary: Use of callbacks to handle accepted endpoints violates design goals. Key: PROTON-1045 URL: https://issues.apache.org/jira/browse/PROTON-1045 Project: Qpid Proton Issue Type: Bug Components: go-binding Affects Versions: 0.11 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.12.0 The electron.Connectoin takes an "accept" callback function to process incoming endpoint requests (sessions, links) This violates the original design goal to have no user code called in the proton goroutine. It relies on the user knowing which functions they are allowed to call in the callback since many user-facing functions can deadlock if called in the proton goroutine. Fix this by having proton provide Incoming requests to the user via a channel. This is also more consistent with typical use of the go net package: when there is something to accept, you start a goroutine to do it, you don't register a callback. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Release Qpid Proton 0.11.0
The artifacts proposed for release are here: https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-rc2/ Please indicate your vote below. If you favor releasing the 0.11.0 RC 2 bits as 0.11.0 GA, vote +1. If you have reason to think RC 2 is not ready for release, vote -1. Thanks! Justin
Proton 0.11.0 release update - RC 2
Hi, everyone. RC 2 is now available: https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-rc2/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheqpid-1049 These bits are signed and versioned for release. If the release vote passes, these RC 2 bits will be the GA bits. RC 2 contains two significant changes since RC 1: https://issues.apache.org/jira/browse/PROTON-949 https://issues.apache.org/jira/browse/PROTON-1042 A big thanks again to those who have tested and reported on previous releases. We're almost there. Justin --- Proton 0.11.0 release page: https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0
[jira] [Commented] (PROTON-1022) 0.11.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000295#comment-15000295 ] ASF subversion and git services commented on PROTON-1022: - Commit ae4449c64b63a61a9ac766f914ca5b876e82cb7d in qpid-proton's branch refs/heads/0.11.x from [~justi9] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=ae4449c ] PROTON-1022: Update versions for 0.11.0 RC 2 > 0.11.0 release tasks > > > Key: PROTON-1022 > URL: https://issues.apache.org/jira/browse/PROTON-1022 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-973) deploying under apache-release profile fails using Java8 due to Javadoc errors
[ https://issues.apache.org/jira/browse/PROTON-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-973: -- Fix Version/s: (was: 0.11) 0.12.0 > deploying under apache-release profile fails using Java8 due to Javadoc errors > -- > > Key: PROTON-973 > URL: https://issues.apache.org/jira/browse/PROTON-973 > Project: Qpid Proton > Issue Type: Task >Affects Versions: 0.10 >Reporter: Robbie Gemmell > Fix For: 0.12.0 > > > There are various javadoc errors when building with Java8 (which is stricter > with syntax) that prevents deploying using the apache-release profile (which > includes javadoc). > The javadoc needs tidied up so it builds on Java8. We should add a check job > in CI that verifies the javadoc has no errors when building with Java8. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-1026) Invalid queue/destination causes a segmentation fault
[ https://issues.apache.org/jira/browse/PROTON-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1026: Fix Version/s: (was: 0.11) 0.12.0 > Invalid queue/destination causes a segmentation fault > - > > Key: PROTON-1026 > URL: https://issues.apache.org/jira/browse/PROTON-1026 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.11 > Environment: Fedora Linux 22, 64bit. > > Using built-in specs. > COLLECT_GCC=/usr/bin/gcc > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.1.1/lto-wrapper > Target: x86_64-redhat-linux > Configured with: ../configure --enable-bootstrap > --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared > --enable-threads=posix --enable-checking=release --enable-multilib > --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions > --enable-gnu-unique-object --enable-linker-build-id > --with-linker-hash-style=gnu --enable-plugin --enable-initfini-array > --disable-libgcj --with-default-libstdcxx-abi=c++98 --with-isl > --enable-libmpx --enable-gnu-indirect-function --with-tune=generic > --with-arch_32=i686 --build=x86_64-redhat-linux > Thread model: posix > gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) > > Compiled with: > cmake -DCMAKE_INSTALL_PREFIX=/opt/devel/qpid-proton-0.11-SNAPSHOT > -DSYSINSTALL_BINDINGS=ON -DBUILD_PYTHON=OFF -DBUILD_PERL=OFF .. > --- >Reporter: Otavio Rodolfo Piske >Assignee: Cliff Jansen >Priority: Critical > Labels: crash > Fix For: 0.12.0 > > Attachments: proton-1026-backtrace.txt > > > Using an invalid path/destination in the address causes the code to crash > with SIGSEGV. > Having the QPid Proton code compiled, please use these teps to reproduce: > 1. Configure a broker > 2. Use the server example to send a message to a non-existent queue: > ./server -a server_address:5672/this_destination_does_no_exist -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-985) Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock time
[ https://issues.apache.org/jira/browse/PROTON-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-985: --- Fix Version/s: (was: 0.11) 0.12.0 > Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock > time > - > > Key: PROTON-985 > URL: https://issues.apache.org/jira/browse/PROTON-985 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.10 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.12.0 > > > The timestamp argument to pn_transport_tick is a pn_timestamp_t. > pn_timestamp_t implies real time (wall clock) in that it's expressed as a > time value based on epoch. > As seen in QPID-6698, using a real time value for that argument can lead to > problems if the real time is adjusted (eg. timezone, daylight savings, > drift). > Instead, pn_transport_tick should be passed a monotonic clock source - one > that does not reflect changes in real time. > All documentation and examples should be updated accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-949) proton doesn't build with ccache swig
[ https://issues.apache.org/jira/browse/PROTON-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-949: --- Fix Version/s: 0.11 > proton doesn't build with ccache swig > - > > Key: PROTON-949 > URL: https://issues.apache.org/jira/browse/PROTON-949 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: michael goulish >Assignee: Alan Conway > Fix For: 0.11, 0.12.0 > > > Thanks to aconway for finding this and saving me a day of madness and horror. > On freshly-downloaded proton tree, if I use this swig: >/usr/lib64/ccache/swig > the build fails this way: > qpid-proton/build/proton-c/bindings/python/cprotonPYTHON_wrap.c:4993:25: > error: 'PN_HANDLE' undeclared (first use in this function) > PNI_PYTRACER = *((PN_HANDLE *)(argp)); > -- > but if I delete that swig executable, and use the one in /bin/swig , > then everything works. > yikes. > aconway believes the bug is in ccache-swig, not in proton, but I want to put > this here in case this bites someone else in Proton Land. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
