Marcel,
The error reporting tool is extremely cool and very useful!
One aspect that could likely be improved significantly is the
computation of the "blamed" projects. In particular I'm having to
triage many reports such as this one:
https://dev.eclipse.org/recommenders/committers/confess/#/problems/54f9b544e4b0a38aecd742e2/details
No doubt that's because Oomph is on the stack:
I would like to suggest that the "blame" logic should consider that
Display.readAndDispatch processes events of arbitrary origin. As such,
nothing below that point in the stack is likely contributing to any
problem above that point in the stack.
Given that Oomph often starts a "background" dialog to perform tasks on
startup, every possible problem that happens elsewhere in the IDE ends
up in Oomph's triage bucket, so the list I must triage is large to the
point where I'm not sure it can ever be managed:
https://dev.eclipse.org/recommenders/committers/confess/#/problems/?projects=oomph&kinds=NORMAL&kinds=FREEZE&categories=UNCONFIRMED&page=1&size=100&sort=createdOn,desc
The duplicates are a bit annoying too, but you have some nice support
for that already:
https://dev.eclipse.org/recommenders/committers/confess/#/problems/5522970ce4b026254ee014bf/similar
Kudos for creating this great technology!
Cheers,
Ed
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
