<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div></div></div><div><blockquote type="cite" class=""><div class="">On 17 May 2016, at 21:50, Doug Hellmann <<a href="mailto:doug@doughellmann.com" class="">doug@doughellmann.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Excerpts from Renat Akhmerov's message of 2016-05-17 19:10:55 +0700:<br class=""><blockquote type="cite" class="">Team,<br class=""><br class="">Our stable/mitaka branch is now broken by oslo.messaging 5.0.0. Global requirements for stable/mitaka has oslo.messaging>=4.0.0 so it can fetch 5.0.0.<br class=""><br class="">Just reminding that it breaks us because we intentionally modified RPCDispatcher like in [1]. It was needed for “at-least-once” delivery. In master we already agreed to remove that hack and work towards having a decent solution (there are options). The patch is [2]. But we need to handle it in mitaka somehow.<br class=""><br class="">Options I see:<br class="">Constrain oslo.messaging in global-requirements.txt for stable/mitaka with 4.6.1. Hard to do since it requires wide cross-project coordination.<br class="">Remove that hack in stable/mitaka as we did with master. It may be bad because this was wanted very much by some of the users<br class=""><br class="">Not sure what else we can do.<br class=""></blockquote><br class="">You could set up your test jobs to use the upper-constraints.txt file in<br class="">the requirements repo.<br class=""></div></div></blockquote><div><br class=""></div>Yes, it’s an option. I’m just thinking from a regular user perspective. There will be a lot of people who don’t know about upper-constraints.txt and they will be stumbling on it just using our requirements.txt. My question here is: is upper-constraints.txt something that’s officially promoted and should be used by everyone or it’s mostly introduced for our internal OpenStack gating system?<br class=""><br class=""><blockquote type="cite" class=""><div class=""><div class="">What was the outcome of the discussion about adding the at-least-once<br class="">semantics to oslo.messaging?<br class=""></div></div></blockquote></div><div class=""><br class=""></div>No outcome yet, we’re still discussing. I expect that more people join the thread since some stakeholders were off after the summit.<br class=""><div class=""><br class=""></div><div class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Renat Akhmerov</div><div class="">@Nokia</div><div class=""><br class=""></div></div></div></div></body></html>