Hi,
Committers can create bug reports from the automatic report in one click. Bug reports are then visible to everyone, including the full stack trace. Since we now have these weekly reports, we’ll discuss today how we can properly leverage them.
Camille
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LE FEVRE FRANCOIS
Envoyé : lundi 6 juillet 2015 09:25
À : Papyrus Project list
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Weekly All Problems Digest for Papyrus
Bonjour,
It is shade because this morning I was really motivated to correct bugs associated with this report since we have asked its generation and sharing a long time
ago.
As I am able to find the class in the code with a grep, I will try to solve the first bug:
NullPointerException in EdgeWithNoSemanticElementRepresentationImpl.hashCode (97)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=471894
I have added no description since I do not have.
I have chosen to add the [Eclipse Error Reports Bot].
Have a good day.
Francois
Yes, only committers can access these reports, because they may contain personal information (Especially ‘how to contact reporters’ and application-specific
information which may be sensitive)
Camille
Same question ^^
Dear all
Good that we have this report.
I have tried to click and logon with my email and the eclipse http password without success.
Do I need special permissions to go on this page?
Francois
Hi,
this is the weekly digest for Papyrus. The status of all problems on this list is open. Items on this list may already be tracked in Bugzilla but were not closed yet. To
remove a item from this list, you can either (i) set the status of its associated bug to resolved, verfied, or closed or (ii) mark it as log message in the reporter's web ui.
If you have any questions about this report, please send an email to
error-reports-inbox@xxxxxxxxxxx
Top new problems (last 7 days):
Top unresolved, active problems (last 7 days):
Top reoccurring problems (last 3 months):
Links:
Thank you for your assistance.
Your friendly error-reports-inbox.
--
You are receiving this email because you are subscribed to alerts of Papyrus. To alter your subscriptions, visit the
project configuration page.