Hi, I have no experience with Sentry.
I just gave it a superquick try and it looks interesting indeed. Since I have no idea how it works exactly and what's possible to do with it, could you quickly describe how it's working together with other issue trackers? Thanks Matthias On 05/03/2018 02:01 PM, Etienne Trimaille wrote: > Having Sentry on a few Python projects, I agree it's a very nice tool to > have for debugging. It shows you new bug, bugs which should be fixed but > occurs again, etc. > It would be nice to have it in QGIS I think. > > 2018-05-03 7:31 GMT-04:00 Patrick Valsecchi > <[email protected] > <mailto:[email protected]>>: > > Hi, > > Would be very useful for QGIS server. Good idea! > > CU > > On Thu, May 3, 2018 at 9:10 AM, Nathan Woodrow <[email protected] > <mailto:[email protected]>> wrote: > > Hey Tim, > > I added a crash handler in 3.0 for Windows at least and it lead > to a few good fixes. I will checkout the stuff you posted to > see if we can intergrate it into what I already have there. > > Nathan > > On Thu, 3 May 2018, 4:43 pm Tim Sutton, <[email protected] > <mailto:[email protected]>> wrote: > > Hi All > > > For many years we have used sentry (http://sentry.io) in our > python projects to systematically collect, review and > prioritise issues raised in our python projects. Sentry.io > <http://Sentry.io> is open source (plus they offer a > commercially hosted service). At Kartoza we run our own > instance under docker / rancher. > > In the last Nødebo hackfest, we discussed the possibility of > using something like Sentry for QGIS so that we could better > understand where our users encounter crashes and proactively > fix them. I subsequently went and researched whether > Sentry.io <http://Sentry.io> has support for mini dumps / > c++ crash handling and at the time it did not have so I > parked thinking about it there. > > Yesterday I got a sentry updates newsletter and noticed that > they have now added C++ support (currently in beta): > > https://blog.sentry.io/2018/04/17/introducing-minidump-support > <https://blog.sentry.io/2018/04/17/introducing-minidump-support> > > I know I am not alone when I run training courses offering > this advice: “Save your project regularly, QGIS will > probably crash at some point”. I really hate saying that but > we have never had a systematic way of seeing where QGIS is > crashing for our users and fixing this crash points. As we > lead up to 3.4 LTR later this year, having good crash > metrics and fixing the most common crash points will allow > us to have a release that we can be confident works well for > our users with out crashing during trivial operations. > > Perhaps one of our fine developers might like to pitch this > as a QGIS Grant proposal (submission period closes 13 May 2018)? > > > http://blog.qgis.org/2018/04/15/qgis-grants-3-call-for-grant-proposals-2018/ > > <http://blog.qgis.org/2018/04/15/qgis-grants-3-call-for-grant-proposals-2018/> > > I’d be happy to help set up our own sentry.io > <http://sentry.io> instance on QGIS infrastructure. We could > also use that instance to receive tracebacks from the python > bits of our code…. > > Regards > > Tim > > — > > > > > > > > *Tim Sutton* > > *Co-founder:* Kartoza > *Ex Project chair:* QGIS.org <http://QGIS.org> > > Visit http://kartoza.com <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 <http://freenode.net> > > _______________________________________________ > QGIS-Developer mailing list > [email protected] > <mailto:[email protected]> > List info: > https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > Unsubscribe: > https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > > _______________________________________________ > QGIS-Developer mailing list > [email protected] > <mailto:[email protected]> > List info: > https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > Unsubscribe: > https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > > > _______________________________________________ > QGIS-Developer mailing list > [email protected] <mailto:[email protected]> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > > > > > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
