On Tue, 14 Aug 2018 at 19:01, Jonathan Moules <jonathan-li...@lightpear.com> wrote: > > Hi Nyall, > > Looking at this from another angle (and being aware I know nothing of > the QGIS code-base) - to me at least that would suggest that maybe it's > worth improving the crash dumps so that they're better able to be used > as a stand-alone debugging thing that doesn't require user feedback/insight. > > Or alternatively make it clear during the crash dump process that the > user needs to supply other information beyond just the file. >
This would certainly help. I'm not sure it's possible, but I'd like to see: 1. A list of all installed/enabled plugins. There's many crash dumps which point to a plugin being at fault, so it'd be nice to identify the troublesome plugins. 2. It should be possible to detect crashes coming from Python code, so we could also do something like disable any python plugins at next load with a warning that one caused a crash. 3. I'm pretty sure this is impossible - but it'd be fantastic to include python backtraces whenever a crash occurs from Python. 4. Including anonymized lists of layers loaded and their general parameters (e.g. provider type) would be beneficial 5. Again, not sure if it's possible, but it'd be great to be able to block reports which are a crash dump only with no futher info on hub itself. Nyall > Cheers, > > Jonathan > > > On 2018-08-14 01:23, Nyall Dawson wrote: > > On Mon, 13 Aug 2018 at 18:11, Paolo Cavallini <cavall...@faunalia.it> wrote: > >> I agree, better be conservative. Furthermore, not always lack of feedback > >> means an issue is not valid. I'd be against automatically closing the > >> issues without further verification. > > I agree in general, but there's a lot of tickets recently with just a > > crash dump (with no clues in the dump) and no further info about how > > to reproduce the crash or what triggered it. These reports don't have > > *any* value on their own. > > > > Nyall > > > >> I'm available to help checking, maybe creating a view of tickets needing a > >> check could be useful. > >> > >> All the best. > >> > >> > >> On 08/13/2018 10:06 AM, Alessandro Pasotti wrote: > >> > >> > >> I would suggest 30 days, people might be so lucky to have their holidays > >> last longer than two weeks. > >> > >> On Mon, Aug 13, 2018 at 2:23 AM, Nyall Dawson <nyall.daw...@gmail.com> > >> wrote: > >>> Quick question re closing issues on redmine: > >>> > >>> What's an "acceptable" amount of time between adding a question to a > >>> ticket/marking as "feedback" before closing that issue as "Closed due > >>> to lack of feedback"? > >>> > >>> Is 14 days sufficient? > >>> > >>> 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 > >> > >> > >> -- > >> Paolo Cavallini - www.faunalia.eu > >> QGIS & PostGIS courses: http://www.faunalia.eu/training.html > >> https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis > >> > >> _______________________________________________ > >> 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 > > > _______________________________________________ > 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
