Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

[Alessandro Pasotti]

Very interesting presentation! Thanks for sharing.

One question: how would SIP behave with STL containers if we decide to use
them instead of Qt containers?

On Fri, Nov 10, 2017 at 12:22 AM, Nyall Dawson 
wrote:

> On 10 November 2017 at 07:29, Nyall Dawson  wrote:
>
> > Is it our preference to use Qt classes and methods wherever available,
> > or should we use std algorithms or raw library methods instead?
>
> On a related note, I'd encourage any QGIS dev to watch KDAB's
> "Effective Qt (2017 edition)" presentation:
>
> https://www.youtube.com/watch?v=uZ68dX1-sVc
>
> Their advice from the first slide:
>
> "Don't use the Qt containers - unless you have to".
>
> And that's coming from KDAB, who are massive contributors to Qt and
> know the framework backwards!
>
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1341] AGRC Geocoding Toolbox approval notification.

[noreply]

Plugin AGRC Geocoding Toolbox approval by zimbogisgeek.
The plugin version "[1341] AGRC Geocoding Toolbox 1.0.0" is now approved
Link: http://plugins.qgis.org/plugins/AGRCGeocodingToolbox/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Maintainer for qgsrasterprojector.cpp

[Tisham Dhar]

Hi All,

I have made a small UI change to add bilinear as a reprojection option when 
sawing raw rasters to file (particularly with reprojection). I am adding 
bilinear reprojection code to "qgsrasterprojector.cpp" block method , sampling 
surrounding row/columns in the source raster in addition to the 
approximateRowCol which the reprojector currently uses. This will slow down 
exports with reprojection and resampling but produce visually more pleasing 
outputs. Could the maintainer for this section please contact me to discuss 
details/changes.

After release is done perhaps.

Regards,

Tisham Dhar
Research Engineer
Aerometrex PTY LTD
59 King William St.
Kent Town SA 5067
Australia

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

[Luigi Pirelli]

super +1, I follow the same rule.
We should add rule for that methods that require pyqt bindings... e.g.
any API should use and return QT containers (just to simplify type
mapping)
Luigi Pirelli

**
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS 2nd Edition:
* 
https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
**


On 9 November 2017 at 22:29, Nyall Dawson  wrote:
> Hi all,
>
> I started a discussion at
> https://github.com/qgis/QGIS/pull/5559#issuecomment-342974170 but I'd
> like greater exposure for this discussion and more feedback, so that
> together we can determine what our preferred development approach is
> for 3.0 and up.
>
> The question is:
>
> 
> Is it our preference to use Qt classes and methods wherever available,
> or should we use std algorithms or raw library methods instead?
> 
>
> The question in that PR results from a choice of either using
> QSqlDatabase methods for accessing a sqlite database OR using some
> basic c++11 wrappers around the raw sqlite3 api.
>
>
> In general my current preference goes something like:
>
> 1. use std implementations
> 2. use qt classes only when they save us work or there's no alternative
>
> Personally I'm just slightly dubious of qt upstream's current ability
> to maintain the qt core and gui libraries, and would prefer to lessen
> our dependence on them (where it makes sense.. i.e. isn't causing us
> more work!)
>
> But I'd like to know everyone's thoughts here, so that we're all
> coordinated with our approaches. I'm happy to go with the consensus
> view here, and would prefer a common approach than a mix of approaches
> across the codebase.
>
> So what's your thoughts?
>
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

[Nyall Dawson]

On 10 November 2017 at 07:29, Nyall Dawson  wrote:

> Is it our preference to use Qt classes and methods wherever available,
> or should we use std algorithms or raw library methods instead?

On a related note, I'd encourage any QGIS dev to watch KDAB's
"Effective Qt (2017 edition)" presentation:

https://www.youtube.com/watch?v=uZ68dX1-sVc

Their advice from the first slide:

"Don't use the Qt containers - unless you have to".

And that's coming from KDAB, who are massive contributors to Qt and
know the framework backwards!

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

[Nyall Dawson]

On 10 November 2017 at 09:02, Even Rouault  wrote:
>> and this should occur also on any platform running qt 5.9
>
>
>
> QT bug filed per
>
> https://bugreports.qt.io/browse/QTBUG-64413

Fantastic work... I'm thinking the Qt project should contract you to
review their codebase!

PR for QGIS at https://github.com/qgis/QGIS/pull/5588

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

[Nathan Woodrow]

Hey,

Personally, I like using the database wrapper that Qt provide and I don't
really see much risk in using it, to be honest.
We might get better speeds going to std route which is something to
consider but I prefer an easier API over raw speed unless it's massive
speed up.

Ideally, we really need to have our own database wrapper which can sit on
top of whatever implementation we choose.  This would also allow us to add
logging of all SQL commands that are run etc.

Regards,
Nathan



On Fri, Nov 10, 2017 at 8:27 AM, Tom Chadwin 
wrote:

> Having suffered at the hands of the QtWebkit thing, I would strongly agree,
> though I guess one airways needs to evaluate the health of any dependency -
> perhaps the are instances where a Qt class is better maintained than the
> alternatives.
>
> Tom
>
>
>
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-
> f4099106.html
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

[Even Rouault]

On vendredi 10 novembre 2017 08:41:53 CET Nyall Dawson wrote:
> On 10 November 2017 at 08:24, Even Rouault  wrote:
> > Digging further this code comes from the dev branch of qt5:
> > https://github.com/qt/qtbase/blob/dev/src/corelib/thread/qsemaphore.cpp#L4
> > 14
> > 
> > Released branches use a different logic:
> > https://github.com/qt/qtbase/blob/5.10/src/corelib/thread/qsemaphore.cpp#L
> > 217
> > 
> > Are you running bleeding edge Qt ?
> 
> No - this was just the osgeo4w dev release, so using 5.9.1.
> 
> Still, maybe it's safest if we just don't use tryAcquire for negative
> timeouts, and instead use acquire explicitly in this case...

Yes, that seems safer

And actually what you observe is logical, since 5.9 is also buggy for a 
dfferent reason since
QSemaphore::tryAcquire(int n, int timeout)
https://github.com/qt/qtbase/blob/5.9/src/corelib/thread/qsemaphore.cpp#L217
calls when timeout < 0
QSemaphore::tryAcquire(int n) which returns false when no resource is free
https://github.com/qt/qtbase/blob/5.9/src/corelib/thread/qsemaphore.cpp#L188

But 5.8 is ok:
https://github.com/qt/qtbase/blob/5.8/src/corelib/thread/qsemaphore.cpp#L217

The regression went per:
https://github.com/qt/qtbase/commit/eaee1209f0ead5be786e81db8aee604ccfea85b0#diff-30e4174ed07523635a22648c06274e0e

and this should occur also on any platform running qt 5.9

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

[Nyall Dawson]

On 10 November 2017 at 08:24, Even Rouault  wrote:

> Digging further this code comes from the dev branch of qt5:
> https://github.com/qt/qtbase/blob/dev/src/corelib/thread/qsemaphore.cpp#L414
>
> Released branches use a different logic:
> https://github.com/qt/qtbase/blob/5.10/src/corelib/thread/qsemaphore.cpp#L217
>
> Are you running bleeding edge Qt ?

No - this was just the osgeo4w dev release, so using 5.9.1.

Still, maybe it's safest if we just don't use tryAcquire for negative
timeouts, and instead use acquire explicitly in this case...

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

[Tom Chadwin]

Having suffered at the hands of the QtWebkit thing, I would strongly agree,
though I guess one airways needs to evaluate the health of any dependency -
perhaps the are instances where a Qt class is better maintained than the
alternatives.

Tom 



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

[Even Rouault]

On jeudi 9 novembre 2017 23:07:11 CET Even Rouault wrote:
> On vendredi 10 novembre 2017 07:24:09 CET Nyall Dawson wrote:
> > Hi all (specifically bugfixing devs)
> > 
> > While doing a bunch of mapping tasks yesterday on master (i.e. being a
> > QGIS user, not a developer!) I hit a bunch of frequent crashes on
> > Windows. Nathan's awesome crash report tool identified the issue as
> > occurring at qgsogrfeatureiterator.cpp:52.
> > 
> > Looking into that some more it seems that the previous line is failing
> > to acquire the connection to the datasource. I can't see anything
> > which would obviously explain this (failing a bug in Qt's
> > QSemaphore::tryAcquire e.g. possibly exposed by 49de489c).
> 
> This hypothesis is not so impossible. I had first a look at Qt4 tryAcquire
> implementation, and I can't see how it would fail. But for Qt5,  I found
> https://code.woboq.org/qt5/qtbase/src/corelib/thread/qsemaphore.cpp.html
> (not sure which point version this is)
> 
> bool QSemaphore::tryAcquire(int n, int timeout)
> {
> Q_ASSERT_X(n >= 0, "QSemaphore::tryAcquire", "parameter 'n' must be
> non-negative"); if (futexAvailable())
> return futexSemaphoreTryAcquire(u, n, timeout < 0 ? -1 :
> timeout); QDeadlineTimer timer(timeout);
> QMutexLocker locker(>mutex);
> qint64 remainingTime = timer.remainingTime();
> while (n > d->avail && remainingTime > 0) {
> if (!d->cond.wait(locker.mutex(), remainingTime))
> return false;
> remainingTime = timer.remainingTime();
> }
> if (n > d->avail)
> return false;
> d->avail -= n;
> return true;
> }

Digging further this code comes from the dev branch of qt5:
https://github.com/qt/qtbase/blob/dev/src/corelib/thread/qsemaphore.cpp#L414

Released branches use a different logic:
https://github.com/qt/qtbase/blob/5.10/src/corelib/thread/qsemaphore.cpp#L217

Are you running bleeding edge Qt ?

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

[Even Rouault]

On vendredi 10 novembre 2017 07:24:09 CET Nyall Dawson wrote:
> Hi all (specifically bugfixing devs)
> 
> While doing a bunch of mapping tasks yesterday on master (i.e. being a
> QGIS user, not a developer!) I hit a bunch of frequent crashes on
> Windows. Nathan's awesome crash report tool identified the issue as
> occurring at qgsogrfeatureiterator.cpp:52.
> 
> Looking into that some more it seems that the previous line is failing
> to acquire the connection to the datasource. I can't see anything
> which would obviously explain this (failing a bug in Qt's
> QSemaphore::tryAcquire e.g. possibly exposed by 49de489c).
> 

This hypothesis is not so impossible. I had first a look at Qt4 tryAcquire 
implementation, and I 
can't see how it would fail. But for Qt5,  I found
https://code.woboq.org/qt5/qtbase/src/corelib/thread/qsemaphore.cpp.html
(not sure which point version this is)

bool QSemaphore::tryAcquire(int n, int timeout)
{
Q_ASSERT_X(n >= 0, "QSemaphore::tryAcquire", "parameter 'n' must be 
non-negative");
if (futexAvailable())
return futexSemaphoreTryAcquire(u, n, timeout < 0 ? -1 : timeout);
QDeadlineTimer timer(timeout);
QMutexLocker locker(>mutex);
qint64 remainingTime = timer.remainingTime();
while (n > d->avail && remainingTime > 0) {
if (!d->cond.wait(locker.mutex(), remainingTime))
return false;
remainingTime = timer.remainingTime();
}
if (n > d->avail)
return false;
d->avail -= n;
return true;
}

Assuming that on Windows futexAvailable() returns false (futex are Linux things 
only, aren't 
they ?), then we go to to the main body

With timeout = -1, timer.remainingTime() will return -1 according to 
QDeadlineTimer doc, so 
the while() loop is not taken. And there, if there's not enough resources 
available, the 
function will return false... Bum !

Hence a Windows only bug, in the not so rare case where the pool has no free 
resource.

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Python error on start up from GRASS processing

[Tim Sutton]

Hi

Thanks Médéric - cleaning out my build dir fixed the issue.

Regards

Tim

> On 09 Nov 2017, at 22:18, Médéric Ribreux  wrote:
> 
> Le 2017-11-09 20:28, Tim Sutton a écrit :
>> Hi
>> Its great to see the GRASS stuff merged now. However it gives me an
>> error on startup:
>> An error has occurred while executing Python code:
>> TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has
>> unexpected type 'ParameterRaster'
>> Traceback (most recent call last):
>>  File
>> "/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins/processing/algs/grass7/Grass7Algorithm.py",
>> line 170, in initAlgorithm
>>res = self.addParameter(p, True)
>> TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has
>> unexpected type 'ParameterRaster'
>> Python version: 3.6.2 (default, Jul 17 2017, 16:44:45) [GCC 4.2.1
>> Compatible Apple LLVM 8.1.0 (clang-802.0.42)]
>> QGIS version: 2.99.0-Master Master, 2c1e2014d7
>> Python Path:
>>  *
>> /Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins/processing
>>  * /Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python
>>  * /Users/timlinux/Library/Application
>> Support/QGIS/QGIS3/profiles/default/python
>>  * /Users/timlinux/Library/Application
>> Support/QGIS/QGIS3/profiles/default/python/plugins
>>  * /Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins
>>  *
>> /Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/bin/$PYTHONPATH
>>  * /usr/local/opt/gdal2-python/lib/python3.6/site-packages
>>  *
>> /usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python36.zip
>>  *
>> /usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6
>>  *
>> /usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload
>>  *
>> /usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages
>>  *
>> /usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pycharm-debug-py3k.egg
>>  * /Users/timlinux/Library/Application
>> Support/QGIS/QGIS3/profiles/default/python
>> Does anyone else get this?
>> Regards
>> Tim
>> —
>> TIM SUTTON
>> CO-FOUNDER: Kartoza
>> PROJECT CHAIR: QGIS.org  [1]
>> Visit http://kartoza.com  [2] to find out about open 
>> source:
>> Desktop GIS programming services
>> Geospatial web development
>> GIS Training
>> Consulting Services
>> SKYPE: timlinux
>> IRC: timlinux on #qgis at freenode.net  [3]
>> Kartoza is a merger between Linfiniti and Afrispatial
>> Links:
>> --
>> [1] http://QGIS.org 
>> [2] http://kartoza.com/ 
>> [3] http://freenode.net 
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org 
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
>> 
> Hello,
> 
> I can't reproduce on a fresh master build. It seems that you are using some 
> old description files (ParameterRaster has been transformed to 
> QgsProcessingParameterRaster).
> I think you need to either start from a clean/new build directory or a new 
> install directory...
> 
> Cheers,
> 
> -- 
> Médéric RIBREUX
> https://medspx.fr 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org 
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
—






Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] discuss: What's our development gameplan for 3.0 and above?

[Nyall Dawson]

Hi all,

I started a discussion at
https://github.com/qgis/QGIS/pull/5559#issuecomment-342974170 but I'd
like greater exposure for this discussion and more feedback, so that
together we can determine what our preferred development approach is
for 3.0 and up.

The question is:


Is it our preference to use Qt classes and methods wherever available,
or should we use std algorithms or raw library methods instead?


The question in that PR results from a choice of either using
QSqlDatabase methods for accessing a sqlite database OR using some
basic c++11 wrappers around the raw sqlite3 api.


In general my current preference goes something like:

1. use std implementations
2. use qt classes only when they save us work or there's no alternative

Personally I'm just slightly dubious of qt upstream's current ability
to maintain the qt core and gui libraries, and would prefer to lessen
our dependence on them (where it makes sense.. i.e. isn't causing us
more work!)

But I'd like to know everyone's thoughts here, so that we're all
coordinated with our approaches. I'm happy to go with the consensus
view here, and would prefer a common approach than a mix of approaches
across the codebase.

So what's your thoughts?

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Crashes in qgsogrfeatureiterator.cpp:52 on master

[Nyall Dawson]

Hi all (specifically bugfixing devs)

While doing a bunch of mapping tasks yesterday on master (i.e. being a
QGIS user, not a developer!) I hit a bunch of frequent crashes on
Windows. Nathan's awesome crash report tool identified the issue as
occurring at qgsogrfeatureiterator.cpp:52.

Looking into that some more it seems that the previous line is failing
to acquire the connection to the datasource. I can't see anything
which would obviously explain this (failing a bug in Qt's
QSemaphore::tryAcquire e.g. possibly exposed by 49de489c).

So this is just a heads up for other devs/testers to be on the lookout
for this and to try and identify any common triggers to encountering
it. I suspect this bug may be the cause of the recent reports of
fragile master builds encountered by testers.

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Python error on start up from GRASS processing

[Médéric Ribreux]

Le 2017-11-09 20:28, Tim Sutton a écrit :

Hi

Its great to see the GRASS stuff merged now. However it gives me an
error on startup:

An error has occurred while executing Python code:

TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has
unexpected type 'ParameterRaster'

Traceback (most recent call last):
  File
"/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins/processing/algs/grass7/Grass7Algorithm.py",
line 170, in initAlgorithm
res = self.addParameter(p, True)
TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has
unexpected type 'ParameterRaster'

Python version: 3.6.2 (default, Jul 17 2017, 16:44:45) [GCC 4.2.1
Compatible Apple LLVM 8.1.0 (clang-802.0.42)]
QGIS version: 2.99.0-Master Master, 2c1e2014d7

Python Path:

*
/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins/processing
* /Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python
* /Users/timlinux/Library/Application
Support/QGIS/QGIS3/profiles/default/python
* /Users/timlinux/Library/Application
Support/QGIS/QGIS3/profiles/default/python/plugins
* /Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins
*
/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/bin/$PYTHONPATH
* /usr/local/opt/gdal2-python/lib/python3.6/site-packages
*
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python36.zip
*
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6
*
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload
*
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages
*
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pycharm-debug-py3k.egg
* /Users/timlinux/Library/Application
Support/QGIS/QGIS3/profiles/default/python

Does anyone else get this?

Regards

Tim

—

TIM SUTTON

CO-FOUNDER: Kartoza
PROJECT CHAIR: QGIS.org [1]

Visit http://kartoza.com [2] to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

SKYPE: timlinux
IRC: timlinux on #qgis at freenode.net [3]

Kartoza is a merger between Linfiniti and Afrispatial


Links:
--
[1] http://QGIS.org
[2] http://kartoza.com/
[3] http://freenode.net
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Hello,

I can't reproduce on a fresh master build. It seems that you are using 
some old description files (ParameterRaster has been transformed to 
QgsProcessingParameterRaster).
I think you need to either start from a clean/new build directory or a 
new install directory...


Cheers,

--
Médéric RIBREUX
https://medspx.fr
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Python error on start up from GRASS processing

[Richard Duivenvoorde]

On 09-11-17 20:28, Tim Sutton wrote:
> Does anyone else get this?
> 

Yep, confirmed here

Richard
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Python error on start up from GRASS processing

[Tim Sutton]

Hi

Its great to see the GRASS stuff merged now. However it gives me an error on 
startup:

An error has occurred while executing Python code: 
TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has unexpected 
type 'ParameterRaster'

Traceback (most recent call last):
  File 
"/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins/processing/algs/grass7/Grass7Algorithm.py",
 line 170, in initAlgorithm
res = self.addParameter(p, True)
TypeError: QgsProcessingAlgorithm.addParameter(): argument 1 has unexpected 
type 'ParameterRaster'

Python version: 3.6.2 (default, Jul 17 2017, 16:44:45) [GCC 4.2.1 Compatible 
Apple LLVM 8.1.0 (clang-802.0.42)] 
QGIS version: 2.99.0-Master Master, 2c1e2014d7 
Python Path:

/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins/processing
/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python
/Users/timlinux/Library/Application Support/QGIS/QGIS3/profiles/default/python
/Users/timlinux/Library/Application 
Support/QGIS/QGIS3/profiles/default/python/plugins
/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/python/plugins
/Users/timlinux/dev/cpp/QGIS-QtCreator-Build/output/bin/$PYTHONPATH
/usr/local/opt/gdal2-python/lib/python3.6/site-packages
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python36.zip
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages
/usr/local/opt/python3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pycharm-debug-py3k.egg
/Users/timlinux/Library/Application Support/QGIS/QGIS3/profiles/default/python

Does anyone else get this?

Regards

Tim



—






Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Handy methods to Copy/Paste Features via QgisInterface

[Germán Carrillo]

Hi qgis-devs,


what do you think about exposing methods to copy/paste features from/to
*given layers* through QgisInterface?

Such methods are available in qgisapp.cpp already [1], but plugin devs
cannot access them. What is exposed right now are the actionCopyFeatures
and actionPasteFeatures, which:

1) Require the layers to be loaded in the QGIS Layer Tree.
2) Require the layers to be active when the corresponding method is called.

There is really no need for those 2 GUI-related requirements.


I've created a Pull Request [2] to make it possible to use source and
target layers for copy/paste operations without loading them into the Layer
Tree, which is much more handy for people using the QGIS API.

That is, you have both layers and just pass them as parameters to the
corresponding copy/paste methods:

>> source_layer.selectAll()
>> iface.copyFeatures(source_layer)
>> target_layer.startEditing()
>> iface.pasteFeatures(target_layer)


*FYI, I'm using copy/paste features functionality to mimic an append
operation from one layer to another, which I've found difficult to achieve
with the API or  even using current Processing algorithms.*


Does it make sense for you?


Regards,

Germán

[1] https://github.com/qgis/QGIS/blob/master/src/app/qgisapp.cpp#L8071-L8192
[2] https://github.com/qgis/QGIS/pull/5578


-- 
---
   |\__
(:>__)(
   |/
Soluciones Geoinformáticas Libres
http://geotux.tuxfamily.org/
http://twitter.com/GeoTux2
http://about.me/germancarrillo


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] pyqgis ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ ΆάϋΎ±ώ≤Ή▌Ίύ ΈίώΪ

[xristosss20]

I try I create a pyqgis standalone script in windows 10 but I have some
errors

first I have read this post

  
and I follow comment of Mr.caiohamamura but I have semi success I think,and
I don't why happen this this error .

first :

Your PYTHONHOME should be:

C:\OSGeo4W64\apps\Python27
Your PATH should include (in the beggining): 
C:\OSGeo4W64\bin; C:\OSGeo4W64\apps\qgis-ltr-dev\bin 
PYTHONPATH should have:

C:\OSGeo4W64\apps\qgis-ltr-dev\python
C:\OSGeo4W64\apps\qgis-ltr-dev\python\plugins
C:\OSGeo4W64\bin\python27.zip
C:\OSGeo4W64\apps\Python27\DLLs
C:\OSGeo4W64\apps\Python27
C:\OSGeo4W64\apps\Python27\lib
C:\OSGeo4W64\apps\Python27\lib\site-packages
and finally the test.

python in cmd prompt:

 

import qgis
from qgis.core import *

all import without error.

python in Osgeo shell :

 

but if i try to import :

import qgis
from qgis.core import *

then i take ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ
ΆάϋΎ±ώ≤Ή▌Ίύ ΈίώΪ.

why in Osgeo shell I take this error :

ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ ΆάϋΎ±ώ≤Ή▌Ίύ
ΈίώΪ.
what I have wrong ?what is the difference?



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] pyqgis ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ ΆάϋΎ±ώ≤Ή▌Ίύ ΈίώΪ

[xristosss20]

I try I create a pyqgis standalone script in windows 10 but I have some
errors

first I have read this post

  
and I follow comment of Mr.caiohamamura but I have semi success I think,and
I don't why happen this this error .

first :

Your PYTHONHOME should be:

C:\OSGeo4W64\apps\Python27
Your PATH should include (in the beggining): 
C:\OSGeo4W64\bin; C:\OSGeo4W64\apps\qgis-ltr-dev\bin 
PYTHONPATH should have:

C:\OSGeo4W64\apps\qgis-ltr-dev\python
C:\OSGeo4W64\apps\qgis-ltr-dev\python\plugins
C:\OSGeo4W64\bin\python27.zip
C:\OSGeo4W64\apps\Python27\DLLs
C:\OSGeo4W64\apps\Python27
C:\OSGeo4W64\apps\Python27\lib
C:\OSGeo4W64\apps\Python27\lib\site-packages
and finally the test.

python in cmd prompt:

 

import qgis
from qgis.core import *

all import without error.

python in Osgeo shell :

 

but if i try to import :

import qgis
from qgis.core import *

then i take ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ
ΆάϋΎ±ώ≤Ή▌Ίύ ΈίώΪ.

why in Osgeo shell I take this error :

ImportError: DLL load failed: ─ίΊ ▐ΪάΊ ϊΫΊάΪⁿ Ίά ίΊΪΎΏώ≤Ϊί▀ ύ ΆάϋΎ±ώ≤Ή▌Ίύ
ΈίώΪ.
what I have wrong ?what is the difference?



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Flaky tests

[Matthias Kuhn]

Hi Even,

Yes, despite things settling again I experienced the same/similar issues.
I can confirm the issues with the spatialite and the locator test.

I am in favor of disabling (parts of) these, since they do more damage
than good in their current state. This will be much appreciated

To avoid this, someone will need to step up and express the requirement
to keep a certain test active for further debugging. In this case it
will be a requirement that an immediate commit follows by "someone" that
will provide more debug information the next time the test fails and
therefore justify leaving it active.

Meanwhile I started with killing any test depending on remote services
in the PyQgsFileDownloader.
https://github.com/qgis/QGIS/pull/5581

Matthias

On 11/09/2017 04:24 PM, Even Rouault wrote:
> Hi,
> 
>  
> 
> I've had a hard time today with a pull request that changed only some
> python test code, but failures occuring in totally unrelated tests. I
> had to restart Travis-CI 5 times before it was green. Had similar issue
> with another PR
> 
>  
> 
> The various failures I got :
> 
>  
> 
> 3 times:
> 
> 359 - PyQgsFileDownloader (Failed)
> 
>  
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=63062502=297409
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061688=297402
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061722=297403
> 
>  
> 
> 1 times:
> 
> 316 - PyQgsRulebasedRenderer (Failed)
> 
>  
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061748=297404
> 
>  
> 
>  
> 
> 1 times:
> 
> 372 - PyQgsServerWMS (Failed)
> 
>  
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061792=297405
> 
>  
> 
> 1 times:
> 
> 328 - PyQgsSpatialiteProvider (Failed)
> 
>  
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061783=297405
> 
>  
> 
>  
> 
> 1 times:
> 
> PyQgsLocator:
> 
>  
> 
> https://dash.orfeo-toolbox.org/testDetails.php?test=61670866=297397
> 
>  
> 
>  
> 
> Anybody already experimented this ?
> 
>  
> 
> Even
> 
>  
> 
> -- 
> 
> Spatialys - Geospatial professional services
> 
> http://www.spatialys.com
> 
> 
> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Flaky tests

[Alessandro Pasotti]

PyQgsLocator is failing 50% of the times for me.

Recently I've been lucky with the others.


On Thu, Nov 9, 2017 at 4:24 PM, Even Rouault 
wrote:

> Hi,
>
>
>
> I've had a hard time today with a pull request that changed only some
> python test code, but failures occuring in totally unrelated tests. I had
> to restart Travis-CI 5 times before it was green. Had similar issue with
> another PR
>
>
>
> The various failures I got :
>
>
>
> 3 times:
>
> 359 - PyQgsFileDownloader (Failed)
>
>
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=63062502=297409
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061688=297402
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061722=297403
>
>
>
> 1 times:
>
> 316 - PyQgsRulebasedRenderer (Failed)
>
>
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061748=297404
>
>
>
>
>
> 1 times:
>
> 372 - PyQgsServerWMS (Failed)
>
>
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061792=297405
>
>
>
> 1 times:
>
> 328 - PyQgsSpatialiteProvider (Failed)
>
>
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=63061783=297405
>
>
>
>
>
> 1 times:
>
> PyQgsLocator:
>
>
>
> https://dash.orfeo-toolbox.org/testDetails.php?test=61670866=297397
>
>
>
>
>
> Anybody already experimented this ?
>
>
>
> Even
>
>
>
> --
>
> Spatialys - Geospatial professional services
>
> http://www.spatialys.com
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Convert from mapunits to pixels

[Tom Chadwin]

Hello all

I've never implemented support of any unit other than pixels in my plugin. A
particular use case (vector tiles) could really use mapunits. Can someone
explain (or point me towards) the method for converting from mapunits to
pixels for on-screen rendering?

Thanks

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Flaky tests

[Tom Chadwin]

I don't know if it's related, but I've had real problems over the last two or
three weeks with Travis tests for a Python plugin. Tests which use an
external resource (a remote WFS) tend to work in the morning (GMT), but fail
in the afternoon. I'm also getting segfaults which I hardly ever get (and
don't really know how to debug in this context).

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QgsServer and 3d tiles

[G. Allegri]

Hi Vincent,
I agree tiled static data can, and should, be served as static content but
what I meant was having something like Tilestache, GeoWebCache, MapCache,
etc.. They're meant to render and cache on the fly, or preseeding the
tileset.

My question raised from the fact that QGIS 3D renderer could be a common
base to produce terrain meshes (a la Cesium) and 3D tiles, both for the
desktop 3D viewer and for a cached tileset to be served through HTTP.
QgsServer could use the same code base to populate the cache, but this
doesn't prevent having a Processing tool (ore whatever) doing the work in
advance.

You're working with gltf. What about OGC I3S?

giovanni

Il 9 nov 2017 16:29, "Vincent Picavet (ml)"  ha
scritto:

Hello,

On 03/11/2017 21:04, G. Allegri wrote:
> What if we had a QgsServer service dedicates to serving 3d tiles for
> Cesium or iTowns?
> Is anybody working on this?

At Oslandia, we work on 3D topics a lot, and 3d tiles in particular. We
are implementing 3D Tiles support in iTowns, and several components to
serve this format as webservices.

E.g. :
- https://github.com/Oslandia/building-server
- https://github.com/Oslandia/lopocs

I do not think having QGIS Server serving 3D tiles is a really good idea.

First, 3D tiles is a format ( and protocol) to serve tiles of objects in
a mostly static way. Therefore, what would be interesting is for QGIS to
have a way to export data as 3d Tiles. These tiles can then be served
with a simple HTTP server, no need for a QGIS Server component.

Moreover, there are a lot of use cases where we want to serve 3D Tiles
without using QGIS at all. Component-oriented architecture is better
than monolithic software.

What I see as best approach would be to mutualize as much code as
possible regarding 3D tiles in py3dtiles :
https://github.com/Oslandia/py3dtiles

Using this module, we can write a 3dtile exporter, as a Processing
module for example. We already have some draft code to do that for some
data sets.
Then, we could have an independant 3D tiles server reusing py3dtiles, or
integrate this as QGIS Server module if we want.

We would be happy to work on these subjects and share our experience on
all 3D-related topics. Funding is also very welcome.

But for now, I think we should focus on releasing QGIS3 in a usable
state. We have waited for too long, and there is still work to achieve
to stabilize the release.

3D features can wait a bit more, even if call for interest, needs,
funding and collaboration is welcome.

Best regards,
Vincent
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QgsServer and 3d tiles

[Vincent Picavet (ml)]

Hello,

On 03/11/2017 21:04, G. Allegri wrote:
> What if we had a QgsServer service dedicates to serving 3d tiles for
> Cesium or iTowns?
> Is anybody working on this?

At Oslandia, we work on 3D topics a lot, and 3d tiles in particular. We
are implementing 3D Tiles support in iTowns, and several components to
serve this format as webservices.

E.g. :
- https://github.com/Oslandia/building-server
- https://github.com/Oslandia/lopocs

I do not think having QGIS Server serving 3D tiles is a really good idea.

First, 3D tiles is a format ( and protocol) to serve tiles of objects in
a mostly static way. Therefore, what would be interesting is for QGIS to
have a way to export data as 3d Tiles. These tiles can then be served
with a simple HTTP server, no need for a QGIS Server component.

Moreover, there are a lot of use cases where we want to serve 3D Tiles
without using QGIS at all. Component-oriented architecture is better
than monolithic software.

What I see as best approach would be to mutualize as much code as
possible regarding 3D tiles in py3dtiles :
https://github.com/Oslandia/py3dtiles

Using this module, we can write a 3dtile exporter, as a Processing
module for example. We already have some draft code to do that for some
data sets.
Then, we could have an independant 3D tiles server reusing py3dtiles, or
integrate this as QGIS Server module if we want.

We would be happy to work on these subjects and share our experience on
all 3D-related topics. Funding is also very welcome.

But for now, I think we should focus on releasing QGIS3 in a usable
state. We have waited for too long, and there is still work to achieve
to stabilize the release.

3D features can wait a bit more, even if call for interest, needs,
funding and collaboration is welcome.

Best regards,
Vincent
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Flaky tests

[Even Rouault]

Hi,

I've had a hard time today with a pull request that changed only some python 
test code, but 
failures occuring in totally unrelated tests. I had to restart Travis-CI 5 
times before it was 
green. Had similar issue with another PR

The various failures I got :

3 times:
359 - PyQgsFileDownloader (Failed)  

https://dash.orfeo-toolbox.org/testDetails.php?test=63062502=297409
https://dash.orfeo-toolbox.org/testDetails.php?test=63061688=297402
https://dash.orfeo-toolbox.org/testDetails.php?test=63061722=297403

1 times:
316 - PyQgsRulebasedRenderer (Failed)

https://dash.orfeo-toolbox.org/testDetails.php?test=63061748=297404


1 times:
372 - PyQgsServerWMS (Failed)

https://dash.orfeo-toolbox.org/testDetails.php?test=63061792=297405

1 times:
328 - PyQgsSpatialiteProvider (Failed)

https://dash.orfeo-toolbox.org/testDetails.php?test=63061783=297405


1 times:
PyQgsLocator:

https://dash.orfeo-toolbox.org/testDetails.php?test=61670866=297397


Anybody already experimented this ?

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1356] ZoomToBelgium approval notification.

[noreply]

Plugin ZoomToBelgium approval by zimbogisgeek.
The plugin version "[1356] ZoomToBelgium 0.1.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/ZoomToBelgium/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1102] AequilibraE approval notification.

[noreply]

Plugin AequilibraE approval by zimbogisgeek.
The plugin version "[1102] AequilibraE 0.3.5.9" is now approved
Link: http://plugins.qgis.org/plugins/AequilibraE/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1246] go2mapillary approval notification.

[noreply]

Plugin go2mapillary approval by zimbogisgeek.
The plugin version "[1246] go2mapillary 1.3" is now approved
Link: http://plugins.qgis.org/plugins/go2mapillary/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1086] SEC4QGIS approval notification.

[noreply]

Plugin SEC4QGIS approval by zimbogisgeek.
The plugin version "[1086] SEC4QGIS 1.0.5" is now approved
Link: http://plugins.qgis.org/plugins/SEC4QGIS/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1066] Isogeo approval notification.

[noreply]

Plugin Isogeo approval by zimbogisgeek.
The plugin version "[1066] Isogeo 1.6.0-beta2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/isogeo_search_engine/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer