3 ms·

At first, I thought my machine was hacked. I didn't know Google Drive was changing their name and the error message I received looked fake: http://i.imgur.com/

by pgrote 10y ago

At first, I thought my machine was hacked. I didn't know Google Drive was changing their name and the error message I received looked fake: http://i.imgur.com/zAJVpAF.png http://i.imgur.com/zAJVpAF.png Notice the grammar and punctuation issues not to mention the email address to nowhere.

PuffinBlue 10y ago
Hmm, that's interesting. Looks like an error message meant for internal Google users. uploader-eng@ would presumably be uploader-eng@google.com The error message also looks like it is also geared towards users with google.com accounts. The whole thing smacks of someone pushing something internal from development to production.
- pgrote 10y ago
  Good point. I hope the details as to how this happened become public. I cannot imagine a release to production can happen without multiple approvals.
  - PuffinBlue 10y ago
    It's definitely quite surprising, especially with Google's SRE strength and multiple automated check systems that have been previously documented here. They often do detailed postmortems so hopefully this one might get that treatment - though given the accidental exposure of the 'not for public release' UI and client they may well not go into much depth with this one.
  - brazzledazzle 10y ago
    Aren't a bunch of approvals an anathema to CI/CD? I have a hard time imagining an old school change management system being tolerated there.
d--b 10y ago
Same here, I was a little freaked out.
citrusui 10y ago
A friend also received the same message: https://twitter.com/resir014/status/842430307538149376 https://twitter.com/resir014/status/842430307538149376 Regarding spelling and grammar, it checks out fine for me. When you're typing a lot of code, it's easier to speak in short sentences and redact useless info (in this case, the @google.com email domain.)

3 ms·

At first, I thought my machine was hacked. I didn't know Google Drive was changing their name and the error message I received looked fake: http://i.imgur.com/

by pgrote 10y ago

PuffinBlue 10y ago
Hmm, that's interesting. Looks like an error message meant for internal Google users. uploader-eng@ would presumably be uploader-eng@google.com The error message also looks like it is also geared towards users with google.com accounts. The whole thing smacks of someone pushing something internal from development to production.
- pgrote 10y ago
  Good point. I hope the details as to how this happened become public. I cannot imagine a release to production can happen without multiple approvals.
  - PuffinBlue 10y ago
    It's definitely quite surprising, especially with Google's SRE strength and multiple automated check systems that have been previously documented here. They often do detailed postmortems so hopefully this one might get that treatment - though given the accidental exposure of the 'not for public release' UI and client they may well not go into much depth with this one.
  - brazzledazzle 10y ago
    Aren't a bunch of approvals an anathema to CI/CD? I have a hard time imagining an old school change management system being tolerated there.
d--b 10y ago
Same here, I was a little freaked out.
citrusui 10y ago
A friend also received the same message: https://twitter.com/resir014/status/842430307538149376 https://twitter.com/resir014/status/842430307538149376 Regarding spelling and grammar, it checks out fine for me. When you're typing a lot of code, it's easier to speak in short sentences and redact useless info (in this case, the @google.com email domain.)