On Thu, Feb 22, 2018 at 12:06 AM, Tony Breeds
wrote:
> On Wed, Feb 21, 2018 at 08:53:09PM +0100, Alfredo Moralejo Alonso wrote:
>
> > Short version is:
> >
> > 1. We generate a review to rdoinfo (RDO's package database) every time a
> > change is detected in upper-constraints.txt proposing it as
On Wed, Feb 21, 2018 at 08:53:09PM +0100, Alfredo Moralejo Alonso wrote:
> Short version is:
>
> 1. We generate a review to rdoinfo (RDO's package database) every time a
> change is detected in upper-constraints.txt proposing it as candidate in
> dependencies repo.
> 2. A job in rdoinfo gate det
On Tue, Feb 20, 2018 at 12:24 AM, Tony Breeds
wrote:
> On Mon, Feb 19, 2018 at 06:10:56PM +0100, Alfredo Moralejo Alonso wrote:
>
> > Recently, we have added a job in post pipeline for openstack/requirements
> > in https://review.rdoproject.org to
> > automatically post updates in RDO dependencie
Hi,
Zane Bitter writes:
> On 17/02/18 16:40, Dan Prince wrote:
>> Thanks for the update Emilien. A couple of things to add:
>>
>> 1) This was really difficult to pin-point via the Heat stack error
>> message ('list index out of range'). I actually had to go and add
>> LOG.debug statements to He
On Mon, Feb 19, 2018 at 03:24:24PM +0100, Bogdan Dobrelya wrote:
> With a backport of the YAQL fixes for tht made for Pike, would it be the
> full fix to make a backport of yaql 1.1.3 for Pike repos as well? Or am I
> missing something?
At some level that should be fine. In the broader OpenSteck
On Mon, Feb 19, 2018 at 06:10:56PM +0100, Alfredo Moralejo Alonso wrote:
> Recently, we have added a job in post pipeline for openstack/requirements
> in https://review.rdoproject.org to
> automatically post updates in RDO dependencies repo when changes are
> detected in upper-constraints. This
>
On 17/02/18 16:40, Dan Prince wrote:
Thanks for the update Emilien. A couple of things to add:
1) This was really difficult to pin-point via the Heat stack error
message ('list index out of range'). I actually had to go and add
LOG.debug statements to Heat to get to the bottom of it. I aim to sy
On Sun, Feb 18, 2018 at 1:35 AM, Tony Breeds
wrote:
> On Sat, Feb 17, 2018 at 04:40:12PM -0500, Dan Prince wrote:
> > Thanks for the update Emilien. A couple of things to add:
> >
> > 1) This was really difficult to pin-point via the Heat stack error
> > message ('list index out of range'). I act
On 2/19/18 3:18 PM, Sofer Athlan-Guyot wrote:
Hi,
Emilien Macchi writes:
Upgrading YAQL from 1.1.0 to 1.1.3 breaks advanced queries with groupBy
aggregation.
The commit that broke it is
https://github.com/openstack/yaql/commit/3fb91784018de335440b01b3b069fe45dc53e025
It broke TripleO: https
Hi,
Emilien Macchi writes:
> Upgrading YAQL from 1.1.0 to 1.1.3 breaks advanced queries with groupBy
> aggregation.
>
> The commit that broke it is
> https://github.com/openstack/yaql/commit/3fb91784018de335440b01b3b069fe45dc53e025
>
> It broke TripleO: https://bugs.launchpad.net/tripleo/+bug/17
Hi,
On Sat, Feb 17, 2018 at 10:40 PM, Dan Prince wrote:
> Thanks for the update Emilien. A couple of things to add:
>
> 1) This was really difficult to pin-point via the Heat stack error
> message ('list index out of range'). I actually had to go and add
> LOG.debug statements to Heat to get to t
On Sat, Feb 17, 2018 at 04:40:12PM -0500, Dan Prince wrote:
> Thanks for the update Emilien. A couple of things to add:
>
> 1) This was really difficult to pin-point via the Heat stack error
> message ('list index out of range'). I actually had to go and add
> LOG.debug statements to Heat to get t
Thanks for the update Emilien. A couple of things to add:
1) This was really difficult to pin-point via the Heat stack error
message ('list index out of range'). I actually had to go and add
LOG.debug statements to Heat to get to the bottom of it. I aim to sync
with a few of the Heat folks next we
On Fri, Feb 16, 2018 at 10:59 PM, Emilien Macchi wrote:
> On Fri, Feb 16, 2018 at 5:36 PM, Emilien Macchi
> wrote:
> [...]
>
>> But Alex and I figured (after a strong headache) that we needed to update
>> the query like this: https://review.openstack.org/545498
>>
>
> To be fully transparent, Al
On Fri, Feb 16, 2018 at 5:36 PM, Emilien Macchi wrote:
[...]
> But Alex and I figured (after a strong headache) that we needed to update
> the query like this: https://review.openstack.org/545498
>
To be fully transparent, Alex and I went ahead and merged the patch but I
have one doubt about thi
15 matches
Mail list logo