6 ms·

Sorry, I think I caused this. =[ bower jquery#1.11.3 not-cached git://github.com/jquery/jquery-dist.git#1.11.3 bower jquery#1.11.

by ikawe 11y ago

Sorry, I think I caused this. =[ bower jquery#1.11.3 not-cached git://github.com/jquery/jquery-dist.git#1.11.3 bower jquery#1.11.3 resolve git://github.com/jquery/jquery-dist.git#1.11.3 bower foundation#~5.5.2 cached git://github.com/zurb/bower-foundation.git#5.5.3 bower foundation#~5.5.2 validate 5.5.3 against git://github.com/zurb/bower-foundation.git#~5.5.2 bower ember#^2.3.0 ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/components/ember.git", exit code of #128 fatal: remote error: Mid bower install. Rly srry guys!!! =[

hartator 11y ago
Cool that you have time to update us. :)
chuhnk 11y ago
I once ran rm -rf in the production mysql data directory. Shit happens.
- ivthreadp110 11y ago
  When I worked at an ecommerce company the boss (who also was a programmer) did that too (on our master engine- not just website orders, but ebay, amazon, everything historical, inventory, RMAs.... etc etc... OOPS indeed... Yep- shit happens. *Recovered from it- was a hastle and shut down everything, but it was one of thoes whoops moments. Happens to the best of us.
- zymhan 11y ago
  I did that too. Destroyed out Zabbix database. Neither that Zabbix server, nor the other one monitoring the server I destroyed, could alert us that anything had gone wrong for over an hour. I finally realized it when I couldn't login... I was able to painstakingly rebuild the server after 9 hours without anyone noticing. To this day one of my biggest fuck ups and prouder accomplishments.
  - postila 11y ago
    Are you saying that once you break something, you should break your monitoring as well, but do it very quickly since it may be too late? :)
    - zymhan 11y ago
      Yeah, if you're going to break your monitoring solution, you'd better shoot it in the head and vaporize the body.
- cflat 11y ago
  You are the human manifestation of "the chaos monkey"
  - thusoy 11y ago
    For anyone that feel they might fall under the same category (I do!), represent: https://teespring.com/human-chaos-monkey https://teespring.com/human-chaos-monkey
- Shizza 11y ago
  I'm going to put that on a T-shirt
  - thusoy 11y ago
    This close enough? https://teespring.com/human-chaos-monkey https://teespring.com/human-chaos-monkey
- AdamJacobMuller 11y ago
  Been there. Done that. No backups. Recovered all the data by using open file handles in /proc/. Not a fun two hours. Shit happens. Live and learn.
  - marco-lavag 11y ago
    Have you written a blog post about that /proc/ trick? sounds like an interesting read
    - teraflop 11y ago
      Here's an article that explains it: http://archive09.linux.com/feature/58142 http://archive09.linux.com/feature/58142
    - AdamJacobMuller 11y ago
      I don't blog, but, what teraflop posted is basically correct.
rdoherty 11y ago
Can someone explain this to people who don't use bower?
- StavrosK 11y ago
  He was just cloning stuff and it failed mid-way.
- deleted 11y ago
  [deleted]
vampolo 11y ago
Oh! i see! So you are the guy that DDoSed github by downloading Ember!
- spiralganglion 11y ago
  I thought the point of heavy client-side frameworks was to take load off the server.
snarkyturtle 11y ago
That's what you get for using bower and jquery. The react/webpack gods are angry.
- ivthreadp110 11y ago
  or the react/webpack gods are laughing...
borismus 11y ago
Maybe by the time you switch to npm, github will come back up?
i336_ 11y ago
So... you were doing a production redeploy, and it crashed? The URL "git://github.com/components/ember.git" [1] suggests this is an internal GitHub Bower build log, but your post history doesn't mention anything about GitHub (let alone whether you work there), so I'm not 100.00% sure. [1] https://webcache.googleusercontent.com/search?q=cache:3e00jlTZDzoJ:https://github.com/components/ember https://webcache.googleusercontent.com/search?q=cache:3e00jl... Assuming this is, in fact, a GH Bower log, the first thing that came to mind was that this architecture isn't (and possibly should be) using a dual-silo approach: when you upgrade, the upgrade gets loaded into a new blank namespace/environment, tested, and if it worked (passes CI test coverage or something like that), the main entry point is switched to the new environment (maybe with a web server restart or config rehash) and the old environment gets purged (possibly after a trial period). The current stack looks quite akin to "click this button to flash the new firmware and DO NOT UNPLUG your device or you'll brick it." But then I realized... wait. You guys have like... isn't it like, a few dozen RoR worker boxes? Was this crash on the inbound router or something? xD It's all good though; consider this "curious criticism" - like constructive criticism, but with extra sympathy. And hey, GH's never broken on my watch before (not that I need it atm... hopefully); this is interesting =P
- spiralganglion 11y ago
  Perhaps you missed the joke?
  - deleted 11y ago
    [deleted]
- gjtorikian 11y ago
  Hate to be the bearer of bad news, but ikawe was joking about the bower thing. Source: I work at GitHub.
  - ivthreadp110 11y ago
    I missed the joke. Either way- hope you get everything up and running soon!

by ikawe 11y ago

hartator 11y ago

Cool that you have time to update us. :)

chuhnk 11y ago

I once ran rm -rf in the production mysql data directory. Shit happens.

ivthreadp110 11y ago
When I worked at an ecommerce company the boss (who also was a programmer) did that too (on our master engine- not just website orders, but ebay, amazon, everything historical, inventory, RMAs.... etc etc... OOPS indeed... Yep- shit happens. *Recovered from it- was a hastle and shut down everything, but it was one of thoes whoops moments. Happens to the best of us.
zymhan 11y ago
I did that too. Destroyed out Zabbix database. Neither that Zabbix server, nor the other one monitoring the server I destroyed, could alert us that anything had gone wrong for over an hour. I finally realized it when I couldn't login... I was able to painstakingly rebuild the server after 9 hours without anyone noticing. To this day one of my biggest fuck ups and prouder accomplishments.
- postila 11y ago
  Are you saying that once you break something, you should break your monitoring as well, but do it very quickly since it may be too late? :)
  - zymhan 11y ago
    Yeah, if you're going to break your monitoring solution, you'd better shoot it in the head and vaporize the body.
cflat 11y ago
You are the human manifestation of "the chaos monkey"
- thusoy 11y ago
  For anyone that feel they might fall under the same category (I do!), represent: https://teespring.com/human-chaos-monkey https://teespring.com/human-chaos-monkey
Shizza 11y ago
I'm going to put that on a T-shirt
- thusoy 11y ago
  This close enough? https://teespring.com/human-chaos-monkey https://teespring.com/human-chaos-monkey
AdamJacobMuller 11y ago
Been there. Done that. No backups. Recovered all the data by using open file handles in /proc/. Not a fun two hours. Shit happens. Live and learn.
- marco-lavag 11y ago
  Have you written a blog post about that /proc/ trick? sounds like an interesting read
  - teraflop 11y ago
    Here's an article that explains it: http://archive09.linux.com/feature/58142 http://archive09.linux.com/feature/58142
  - AdamJacobMuller 11y ago
    I don't blog, but, what teraflop posted is basically correct.

rdoherty 11y ago

Can someone explain this to people who don't use bower?

StavrosK 11y ago
He was just cloning stuff and it failed mid-way.
deleted 11y ago
[deleted]

vampolo 11y ago

Oh! i see! So you are the guy that DDoSed github by downloading Ember!

spiralganglion 11y ago
I thought the point of heavy client-side frameworks was to take load off the server.

snarkyturtle 11y ago

That's what you get for using bower and jquery. The react/webpack gods are angry.

ivthreadp110 11y ago
or the react/webpack gods are laughing...

borismus 11y ago

Maybe by the time you switch to npm, github will come back up?

i336_ 11y ago

So... you were doing a production redeploy, and it crashed? The URL "git://github.com/components/ember.git" [1] suggests this is an internal GitHub Bower build log, but your post history doesn't mention anything about GitHub (let alone whether you work there), so I'm not 100.00% sure. [1] https://webcache.googleusercontent.com/search?q=cache:3e00jlTZDzoJ:https://github.com/components/ember https://webcache.googleusercontent.com/search?q=cache:3e00jl... Assuming this is, in fact, a GH Bower log, the first thing that came to mind was that this architecture isn't (and possibly should be) using a dual-silo approach: when you upgrade, the upgrade gets loaded into a new blank namespace/environment, tested, and if it worked (passes CI test coverage or something like that), the main entry point is switched to the new environment (maybe with a web server restart or config rehash) and the old environment gets purged (possibly after a trial period). The current stack looks quite akin to "click this button to flash the new firmware and DO NOT UNPLUG your device or you'll brick it." But then I realized... wait. You guys have like... isn't it like, a few dozen RoR worker boxes? Was this crash on the inbound router or something? xD It's all good though; consider this "curious criticism" - like constructive criticism, but with extra sympathy. And hey, GH's never broken on my watch before (not that I need it atm... hopefully); this is interesting =P

spiralganglion 11y ago
Perhaps you missed the joke?
- deleted 11y ago
  [deleted]
gjtorikian 11y ago
Hate to be the bearer of bad news, but ikawe was joking about the bower thing. Source: I work at GitHub.
- ivthreadp110 11y ago
  I missed the joke. Either way- hope you get everything up and running soon!