Hi, So I found out the culprit and it was not my fault.
I was looking at a plugin to replace the buggy "Github PR" tool and looked GerritForge that I setup *only* on my account to I could use it to look at the PR and how it compares to the Github interface. It's basically a Gerrit instance for gtihub. They went nuts and FORCED pushed stuff using my key. WHAT? This is wrong. We should contact github to get our stuff rolled backed. Thanks. ---------- Forwarded message ---------- From: GerritForge Support <supp...@gerritforge.com> Date: Sun, Nov 10, 2013 at 6:52 PM Subject: AW - Temporary GerritHub.io replication glitch To: darktear...@gmail.com Dear Alexis Menard we are writing to inform about a *GerritHub.io replication glitch that impacted some of our users in the past 24 hours*. Please *read this e-mail carefully to assess the situation with your repositories hosted on GitHub*. *Q: What was the glitch about ?* GerritHub.io had his replication system stopped for about 2 weeks: this means that the changes made on GerritHub.io were stored in the Gerrit repositories without being replicated to GitHub. *Q: Has the problem been resolved ?* The problem was partially resolved this morning (Sun 10th of November, 02:13 AM GMT) and GerritHub.io triggered a resynch of all repositories to GitHub. The following repositories have been *forced pushed* from the latest commits in GerritHub.io to GitHub: crosswalk-project/brackets-crosswalk.git crosswalk-project/crosswalk-demos.git crosswalk-project/crosswalk.git crosswalk-project/crosswalk-website.git crosswalk-project/tizen-extensions-crosswa *Q: What is required on my side ?* It depends if you fit into one of the two following cases: Case A: If you have been always pushing to GerritHub.io, the synch should have now brought all those pushes to GitHub as well. Everything should be now up-to-date on both sides. Case B: If you noticed the problem and have then just pushed on GitHub (without going through GerritHub.io), the forced push performed by GerritHub.io have then brought your branches back. *Q: I am in Case B, what should I do to recover my commits ?* Your commits are still on both your local clone and on GitHub as well: you need just to move again the pointer back to where it was before. >From your local Git clone (or the Git clone on the CI server), you need perform the following two commands: (to restore the GitHub pointers) git push origin (to align the points on GerritHub.io as well) git push ssh://<username>@gerrithub.io:29418/<username>/<repository> *Q: Am I safe now ? Would the problem happen again ?* Yes, you are safe: we are changing the Gerrit replication in order to avoid the force push altogether and then prevent this problem to happen again in the future. GitHub and GerritHub.io will naturally align to the latest branch point, whichever is the most recent. No forced push will be used anymore on the GerritHub.io side. *Q: I have further questions: who can I talk to ?* If you have further questions or doubts, please contact GerritForge Support through one of the following channels: *Fax: +44 (0) 203 318-3620 <%2B44%20%280%29%20203%20318-3620>* *Phone UK: +44-(0) 208 144-9448 <%2B44-%280%29%20208%20144-9448>Phone USA: +1-(650) 741-1436 <%2B1-%28650%29%20741-1436>Phone AUS: +61-(0)280 911448 <%2B61-%280%29280%20911448>* *eMail: supp...@gerritforge.com <supp...@gerritforge.com>* *Skype: gerrit.support* *Twitter: @gitenterprise* --- * --- Thank you for your renewed confidence in our service and feel free to share your feedback on Twitter @gitenterprise. --- GerritForge *Support* http://www.gerritforge.com *supp...@gerritforge.com <supp...@gerritforge.com>* Fax: +44 (0) 203 318-3620 UK: +44-(0) 208 144-9448 US: +1-(650) 741-1436 AU: +61-(0)280 911448 *Skype: gerrit.support* -- Alexis Menard Software Engineer @ Intel Open Source Technology Center Intel Semiconductores do Brasil Ltda. Ave Dr. Chucri Zaidan, 940, Brooklin, 10 Andar 04583-904 São Paulo, SP Brazil This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
