Hi all,
Currently I'm experiencing very slow work of Gerrit (since yesterday) to
the extent that I cannot work with it effectively.
Does anyone else have the same problem with it?
I've tried to connect to it from different locations and vpn and the speed
of gerrit is low everywhere.
Thanks,
I am experiencing the same thing, but it seems like my colleagues do not. I
was thinking it was just me.
I'll invoke the oncall people.
On Wed, Aug 27, 2014 at 1:46 PM, Andrei Korzhevskii a.korzhevs...@gmail.com
wrote:
Hi all,
Currently I'm experiencing very slow work of Gerrit (since
Yeah it was unusable for me too but now it works again however it is still
pretty slow for me.
-- J.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
This should be resolved now.
On Wednesday, August 27, 2014 2:13:48 PM UTC+2, Jens wrote:
Yeah it was unusable for me too but now it works again however it is still
pretty slow for me.
-- J.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors
It's alive! Thank you, Daniel.
On Wednesday, August 27, 2014 6:57:56 PM UTC+4, Daniel Kurka wrote:
This should be resolved now.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails
Any updates?
On Sunday, August 17, 2014 10:03:34 AM UTC-6, Thomas Broyer wrote:
We (the Steering Committee) will meet next week to discuss specifically
about this.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this
We decided that we are holding GWT 2.7 for the new per file compilation and
GSS support.
Both of them are shaping up to be really cool features, but are not done
yet. As soon as we consider them done (being live within google and not
causing issues anymore), we will put out a release candidate.
As I'm sure everyone is aware, IE11 is making the navigator.useragent
property significantly more useless than it already was, by having IE11
identify as 'Trident' rather than 'MSIE', and adding 'iPhone', 'Webkit',
'Android' and a few other obviously garbage strings.
Check out
On Wed, Aug 27, 2014 at 2:52 PM, Colin Alworth niloc...@gmail.com wrote:
As I'm sure everyone is aware, IE11 is making the navigator.useragent
property significantly more useless than it already was, by having IE11
identify as 'Trident' rather than 'MSIE', and adding 'iPhone', 'Webkit',
