On 06/12/2015 01:15 AM, Marcel Bruch wrote:
We are now looking forward to the first two weeks of the Mars release
and cross fingers that we don’t get flooded.
Marcel,
Do we have an OFF switch somewhere so that we can turn these things off
if we see we're going to get flooded?
I don't have
I see your point. Having a cross-workspaces history was something we discussed
lately but I had not enough time to think it through and implement it. The
request was closed as won fix because there are several alternatives:
If 50 users reported the same error, it will be added to the remote
Hi Marcel,
This is looking good. But I’m a bit concerned about “Level 1” - If you have a
dozen workspaces, I don’t think I’m the only one, you will still produce
excessive error reports. Also I do keep hitting the same error again and again,
but choose to not send (because I know the reason).
If it is a matter of beer...
it's going to cost you a fortune in beer at EclipseCon.
I vote for no off switch! ;)
Jay
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your
cost you a fortune in beer at EclipseCon
Two questions:
1. Which one (EclipseCon) will you attend?
2. How long does your short-term memory last?
On 12 Jun 2015, at 15:03, Denis Roy denis@eclipse.org wrote:
On 06/12/2015 01:15 AM, Marcel Bruch wrote:
We are now looking forward
On 12 Jun 2015, at 15:03, Denis Roy denis@eclipse.org wrote:
On 06/12/2015 01:15 AM, Marcel Bruch wrote:
We are now looking forward to the first two weeks of the Mars release
and cross fingers that we don’t get flooded.
Marcel,
Do we have an OFF switch somewhere so that we can
On 06/12/2015 01:15 AM, Marcel Bruch wrote:
We are now looking forward to the first two weeks of the Mars release
and cross fingers that we don’t get flooded.
Marcel,
Do we have an OFF switch somewhere so that we can turn these things
off if we see we're going to get flooded?
Have
Denis,
there are four (4) + one (1) mechanisms in place that will / can limit the
traffic to dev.eclipse.org/recommenders:
Level 1: A local, persistent, per-workspace history that remembers what was
send before. If an error is logged that has the same fingerprint as an already
sent report, it
It appears to me that you didn't just write code; you've engineered a
solution.
No need for crossed fingers. I think we're in good shape. Beer will be
on me at EclipseCon.
Have a nice weekend.
Denis
On 12/06/15 02:21 PM, Marcel Bruch wrote:
Denis,
there are four (4) + one (1)
