The problem you are describing is because of the evaluative nature of
the current setup, where I was asked to force the entire system to
have limited exposure. In full rollout every report that the user
manually writes in drkonqi will also end up on sentry. Every
additional crash also, so long as
On Mon, Jun 12, 2023 at 11:39 PM David Edmundson
wrote:
> I'm not sure the teams and groups really work out right now. Do we
> need to request access to groups and have that approved?
That is how it used to be, yes. I've just sprinkled some code at the
instance that should allow us to forgo the
>Did you like it?
When we had an initial influx of reports after you first blogged it
was amazing. We were getting reports in places I hadn't seen before on
bugzilla.
It did a really good job of implicitly showing which things were the
most relevant needing fixing, and what's just noise we can
On Sun, Jun 11, 2023 at 7:13 PM Albert Vaca Cintora
wrote:
>
> I didn't know we had Sentry! How can we get crash reports from KDE
> Connect through it?
Because this isn't widely rolled out yet, due to evaluation period,
there's only limited data for kdeconnect. Here's one:
I didn't know we had Sentry! How can we get crash reports from KDE
Connect through it? That would be super useful. I've used Sentry in
the past for other projects and I see a big value in it.
Actually, in the case of the KDE Connect Android app, we already get
crash reports aggregated by
On Mon, Jun 5, 2023 at 12:20 AM Albert Astals Cid wrote:
>
> El dijous, 1 de juny de 2023, a les 12:35:41 (CEST), Harald Sitter va
> escriure:
> > Hey,
> >
> > We've had almost a year, albeit in a super limited capacity for git
> > builds, with sentry (https://errors-eval.kde.org) and we should
>
El dijous, 1 de juny de 2023, a les 12:35:41 (CEST), Harald Sitter va
escriure:
> Hey,
>
> We've had almost a year, albeit in a super limited capacity for git
> builds, with sentry (https://errors-eval.kde.org) and we should
> probably render a final verdict on the evaluation.
>
> Did you like
I think it has been a good tool. There's some problems that are simply
too hard to report using bugzilla and these can be analyzed
accordingly. In the end, they are all problems that exist and users
face. I understand it's a problem that we don't really get the context
in these but maybe it's just
Hi!
Nate Graham writes:
> To be honest, I haven’t found Sentry to be that useful in its current
> implementation. The primary issue is that it represents a second source of
> truth
> for where crash reports live. As a result, developers who already struggle to
> notice Bugzilla-based crash
To be honest, I haven't found Sentry to be that useful in its current
implementation. The primary issue is that it represents a second source
of truth for where crash reports live. As a result, developers who
already struggle to notice Bugzilla-based crash reports have to look in
a second
10 matches
Mail list logo
