Re: [epp-dev] Adding a error log collector to Mars milestone builds?

[Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>]

Wayne,

I get the feeling that getting the permission to add this to the packages will take a (long) while. M5 will be in 5*6weeks = longer than I can count…

Is there a chance to get s simpler solution rolled out?

Say:

Let’s trim the messages after 140 chars. There can’t be much source code in it, right?

Or if you still have concerns: let’s skip the message completely. the stacktrace is what we need anyways to fix issues.

Would this be a viable alternative for the moment?

Marcel

Am 12.08.2014 um 21:58 schrieb Wayne Beaton <wayne@xxxxxxxxxxx>:

Wouldn't it make more sense to filter on "----------------------------------- SOURCE BEGIN -------------------------------------" ?

Or trim the message after the first line?

Unfortunately, I think that the general rule is to filter on anything that "looks like code". We can probably use some simple heuristics to get this right most of the time, but I'm concerned that there will be corner cases with potential for private/identifiable data to be leaked.

Perhaps it's enough to ask the user for permission to send the information. We may, for example, require that there be some reasonable means for the user to review the full content of the message that gets sent.

Wayne

On 12/08/14 02:48 PM, Marcel Bruch wrote:

For source code: I think it’s possible to identify source code by looking for many „import" statements in the message.

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
<ECE Friends 480x60.png>

_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev