Re: [Tiki-devel] Using GlitchTip as part of the Tiki development process

> So if a developer is helping you, you can provide them access and it may help them

I understand.

When I create a ticket, if I can reproduce on a Tiki site where Glitchtip is set and produce a report I will add it to the ticket (or specify it exist).

Regards,
Bernard






> On 10 Apr 2023, at 2:31, [email protected] wrote:
> 
> Short answer: as of now, this is mostly for developers. So if a developer is helping you, you can provide them access and it may help them. And they can provide a MR to solve.
> 
> 
> Long answer:
> 
> A few months ago, our dev/test site running Tiki master (which was pretty close to 25x) was provoking over 100 000k events for a month. A single sub-optimal piece of Tiki code can provoke dozens of events on each page load. So this adds up. GlitchTip helps us prioritize by counting and sorting the event/errors.
> 
> Most of the errors are harmless. Ex.: https://gitlab.com/tikiwiki/tiki/-/merge_requests/2414/diffs
> But some of them helped uncover a real underlying issue. Ex.: https://gitlab.com/tikiwiki/tiki/-/merge_requests/2400
> 
> I estimate that we have fixed a few hundred so far, and we have a few hundred more to fix.
> 
> Jean-Marc fixed over 40: https://www.openhub.net/p/tikiwiki/contributors/167504554652 and we have over 10 developers working on this.
> 
> A few Tiki versions ago, the unified index rebuild log was noisy, and now, it's clean. So when something appears there, it's easy to catch. And usually gets fixed quickly because we all want to keep it clean: https://en.wikipedia.org/wiki/Broken_windows_theory
> 
> For what GlitchTip is catching, we are not there yet. I hope we'll be there before 26x is branched, but it will be tight. But we'll continue on this for as long as it takes.
> 
> Once we have finished cleaning the errors, we'll likely open the dev site to volunteers so they can attempt to provoke errors, so our devs can address them.
> 
> Best regards,
> 
> Marc
> 
> 
> 
> 
> 
> 
> On 2023-04-04 04:49, Bernard Sfez via TikiWiki-devel wrote:
>> Hello Marc,
>> Today (and out of curiosity) I setup Glitchtip on my own Tiki (and
>> improved the documentation) ;-)
>> While it is interesting to see inside a Ferrari engine 🤭, is something
>> expected from here for “non” developer users to improve Tiki code ?
>> Practically, I have a report for an issue should I do something ?
>> ErrorException /lib/trackers/trackerlib.php in TrackerLib::replace_item
>> Warning: Invalid argument supplied for foreach()
>> —
>> Bernard
>> PS: I have no more clue about it as I don’t see anything on the user
>> side. Not even sure how it was triggered.
>>> On 3 Mar 2023, at 23:47, Marc Laporte <[email protected]> wrote:
>>> Dear Tiki community,
>>> GlitchTip is an Open Source error tracking system (can also do uptime monitoring) and you can self-host GlitchTip or subscribe to GlitchTip.com (including a free starter plan). Tiki and GlitchTip interoperability was added in Tiki23. Starting in March 2023, we are using GlitchTip as a part of the development process.
>>> Please see:
>>> https://dev.tiki.org/Using-GlitchTip-as-part-of-the-Tiki-development-process
>>> _______________________________________________
>>> TikiWiki-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>> _______________________________________________
>> TikiWiki-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> 
> 
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel



_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel