Currently there's an inconsistancy between the Options dialog that displays a
default value of 60000ms for network request timeouts, whereas places in the
code use 20000ms. I propose to align on 60000s, since there are occurrences
of network requests, for example big WFS GetFeature requests, that can take
more than 20s to start.
Currently sqlite3_bind_blob() uses free() as the free function of WKB
blobs returned by convertFromGeosWKB(). But those are allocated with
new[] and should consequently be freed with delete[].
Spotted by Valgrind:
==4014== Mismatched free() / delete / delete []
==4014== at 0x4C287BE: free (vg_replace_malloc.c:446)
==4014== by 0xE42E481: sqlite3VdbeMemReleaseExternal (sqlite3.c:57237)
==4014== by 0xE42E4E3: sqlite3VdbeMemRelease (sqlite3.c:57252)
==4014== by 0xE42EC3E: releaseMemArray (sqlite3.c:59208)
==4014== by 0xE42ED1E: sqlite3VdbeDeleteObject (sqlite3.c:60561)
==4014== by 0xE46A6DB: sqlite3VdbeFinalize (sqlite3.c:60528)
==4014== by 0xE46A916: sqlite3_finalize (sqlite3.c:61431)
==4014== by 0x7FB23958: QgsSpatiaLiteProvider::addFeatures(QList<QgsFeature>&) (qgsspatialiteprovider.cpp:3752)
==4014== Address 0x8e2a8b30 is 0 bytes inside a block of size 94 alloc'd
==4014== at 0x4C29520: operator new[](unsigned long) (vg_replace_malloc.c:363)
==4014== by 0x7FB1B964: QgsSpatiaLiteProvider::convertFromGeosWKB(unsigned char const*, int, unsigned char**, int*, int) (qgsspatialiteprovider.cpp:1341)
==4014== by 0x7FB234B5: QgsSpatiaLiteProvider::addFeatures(QList<QgsFeature>&) (qgsspatialiteprovider.cpp:3676)
[processing] fix filter in Processing settings dialog. Add ability to specify mininal required number of items for MultipleInput parameter (fix#11469, fix#12580)
* drop libpasteurize.fixes.fix_division
* replace lib2to3.fixes.fix_import with libfuturize.fixes.fix_absolute_import (with PyQt exclude plus AlgorithmsTestBase)
* drop lib2to3.fixes.fix_print (replaced with libfuturize.fixes.fix_print_with_import)
