Re: [Development] CI problems

2017-05-18 Thread Tuukka Turunen
Awesome. Thanks, Tony (and others who worked to get this resolved quickly)! Yours, Tuukka From: Development on behalf of Tony Sarajärvi Date: Thursday, 18 May 2017 at 22.46 To: "development@qt-project.org" Subject: Re: [Development] CI problems (Apparently it was just my ow

Re: [Development] CI problems

2017-05-18 Thread Tony Sarajärvi
(Apparently it was just my own inbox not being updated 😉) It now looks like we have a running CI again! I started Coin and everything seems to be running as normal. I’ll keep watching it for a while longer and then resume work in the morning. Thanks for your patience. -Tony From: Development

[Development] CI problems

2017-05-18 Thread Tony Sarajärvi
Hi Seems my earlier 2 mails haven't reached you. I hope this one does. We've suffered hardware malfunction today. Our CI environment began behaving oddly aprox 20 hours ago and early this morning we noticed that not everything was OK. To prevent data loss and further problems, we shut down the

Re: [Development] CI is down again

2017-05-18 Thread Tony Sarajärvi
Update: Dell is investigating problems with the Compellent (our backend storage system). We're seeing huge latencies over our fiber optics there and the system can't be used atm. Their 24/7 crew is working on it as their P1. -Tony -- Update: We're unsure why we a going at c

Re: [Development] Introducing discussion about QStringFormatter

2017-05-18 Thread Thiago Macieira
On Thursday, 18 May 2017 02:57:43 PDT Mårten Nordheim wrote: > But to clarify, in your scenario > "{}{}" % ("a", "b") > would be "ab", correct? That's what I would expect, yes. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center __

Re: [Development] Introducing discussion about QStringFormatter

2017-05-18 Thread Thiago Macieira
On Thursday, 18 May 2017 02:39:36 PDT Mårten Nordheim wrote: > > Please consider, in terms of Qt API design (ease of use, surprise factor, > > etc.) just what the following should do: > > > > QStringFormatter("%1 is {1}").arg("foo").subs("bar") > > Hm, hadn't thought that far ahead, thanks. I gue

Re: [Development] Stepping down as QtDBus maintainer

2017-05-18 Thread Thiago Macieira
On Thursday, 18 May 2017 03:01:08 PDT Sergio Martins wrote: > On 2017-05-17 17:19, Thiago Macieira wrote: > > Since I am unable to fulfill my duties as maintainer, I am stepping > > down and > > opening the way up for someone else. > > Hi Thiago, > > Do you have an overview on what's the current

Re: [Development] Stepping down as QtDBus maintainer

2017-05-18 Thread Thiago Macieira
On Thursday, 18 May 2017 03:58:19 PDT Frederik Gladhorn wrote: > Isn't that a bit premature? Maybe someone could use these as inspiration. > I'd like to see us (as in The Qt Project) be more flexible when it comes to > ownership of patches - maybe someone feels inspired to take over some of > the w

Re: [Development] CI is down again

2017-05-18 Thread Tony Sarajärvi
Update: We're unsure why we a going at crawling speed on some parts of our infra. We could be facing hardware issues since we have restarted almost everything we have. Investigations are ongoing, and I can't give an ETA currently as to when we come back online. We need to find the reason first.

Re: [Development] Stepping down as QtDBus maintainer

2017-05-18 Thread Frederik Gladhorn
Hello Thiago, Thanks a lot for all the great work on QtDBus! Cheers, Frederik On onsdag 17. mai 2017 09.19.13 CEST Thiago Macieira wrote: > With https://codereview.qt-project.org/194893 getting integrated, this > signals my inability to keep QtDBus working for 4 minor releases in a row > (5.6 th

Re: [Development] Stepping down as QtDBus maintainer

2017-05-18 Thread Lars Knoll
Hi Thiago, thanks for all the efforts you’ve been putting into it over the years. > On 17 May 2017, at 18:19, Thiago Macieira wrote: > > With https://codereview.qt-project.org/194893 getting integrated, this > signals > my inability to keep QtDBus working for 4 minor releases in a row (5.6

Re: [Development] Stepping down as QtDBus maintainer

2017-05-18 Thread Sergio Martins
On 2017-05-17 17:19, Thiago Macieira wrote: Since I am unable to fulfill my duties as maintainer, I am stepping down and opening the way up for someone else. Hi Thiago, Do you have an overview on what's the current state of the module ? Just so the next maintainer gets an idea of where to st

Re: [Development] Introducing discussion about QStringFormatter

2017-05-18 Thread Mårten Nordheim
On 16.05.2017 19:14, Thiago Macieira wrote: On {}{}: I think that's an acceptable shorthand, just like we have "%1 is %1" today. A bracket without any digits has higher replacement precedence than {0}: "The {0} brown {} jumped over the {2} {3}" % ("fox", "quick", "dog", "lazy") {} gets repla

Re: [Development] Introducing discussion about QStringFormatter

2017-05-18 Thread Mårten Nordheim
On 16.05.2017 19:23, Thiago Macieira wrote: On segunda-feira, 15 de maio de 2017 05:49:19 PDT Mårten Nordheim wrote: - Note: To print a curly brace they have to be doubled (same as in all of the above) ( "{{", "}}" ) Why do we need a double closing curly brace?

Re: [Development] QList

2017-05-18 Thread Ville Voutilainen
On 27 April 2017 at 17:57, Thiago Macieira wrote: > On Thursday, 27 April 2017 01:19:16 -03 Marc Mutz wrote: >> On 2017-04-26 23:38, Konstantin Tokarev wrote: >> > 26.04.2017, 08:04, "Marc Mutz" : >> >> Users >> >> that need a queue can use std::deque. If you don't iterate over it, >> >> it's >> >