Tal, Yes, this bug is super-nasty. We've been looking at it for a month, and unfortunately it's at the intersection of our data center infrastructure, serving infrastructure, and our Git backends. And, naturally, there isn't much logging at the edges of these systems.
As Yash commented on the bug, we have been working on a speculative fix and will be rolling that out either tomorrow or early early next week. Best case scenario you won't see this again. Worst case scenario we might need to continue investigating and turn the crank again. Regardless, we will keep you posted. While we haven't kept the bug up to date with every step we've made, I assure you we've taken this issue very seriously. I agree we can improve our transparency on things like this; but the majority of issues haven't taken this long to get resolved. Thanks, -Chris Smith On Wednesday, September 5, 2012 3:39:32 PM UTC-7, Tal Liron wrote: > > For more than a month now there has been an unresolved open issue that is > breaking the ability of many, many projects to push code to Google Code > hosting: > > http://code.google.com/p/support/issues/detail?id=28389 > > The issue, in essence, is that large chunks of data coming in via git and > hg push (possible also svn?) result in 502 errors, and the push fails. > Looking back into Google Code support history, it seems that this issue has > happened from time to time and has been resolved. But it's back again. > > I must say that I'm astounded and disappointed by the lack of attention > this open wound has been getting. There should be warnings plastered > everywhere on Google Code about this, and constant communication with the > developer community in the blogs, twitters, google-pluses, and of course in > the issue page itself. You've let it up to us devs to debug things on our > end and search hard to find out that it's your fault, not ours, and that > you've known about it for more than a month. We want to spend time writing > good code, not rediscovering information that's already known. > > Google Code team: you are dealing with this terribly and it won't be long > before this escalates into a PR disaster, with projects leaving you in > hordes. I really hope someone on the team gets some sense, takes charge and > deals with this professionally. I love Google Code's features and would not > want to move my many projects to GitHub, but patience is running thin and > soon there will be no choice. > > I'm saying this with love: I hate to see something good go down the drain > due to poor leadership. > > Your friend, > Tal > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-code-hosting/-/TgjNFS9q45EJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
