ERROR: The following plug-in has crashed: Shockwave Flash
WTF is going on? Google Chrome is the best, most stable browser out there. Is it a problem with the page/site I’m on?
Other than the page/site being in flash, which is a whole ‘nother problem of itself, it’s not the page/site. It’s the internal Flash plugin in Google Chrome.
Yeah, but how? Why?
Every once in a while, Google Chrome auto-updates itself and unless you check the About Google Chrome page, you will never know, as it happens “automagically.” Part of the auto-update are the plugins that are bundled with the browser. Sometimes those plugins get updated too. The reason that you are getting a crash is there is a conflict between the Flash plugin that gets bundled with Google Chrome and the Flash plugin installed on your OS, used by your non-Chrome browsers.
I joined GitHub in June of 2012, just to see what the fuss was all about. It wasn’t until today that I had my first pull request accepted and merged, and it was that feeling of having contributed to something that others may find useful that inspired me to write this post. The inspiration doesn’t come from the contributing part. Don’t get me wrong. I’ve contributed and collaborated before. It was, rather, this new social way of controlling and tracking code, changesets, and comments that really make GitHub… cool.
Origins & Centralized Code Control
My origins with source code control stemmed from the days of Microsoft Visual SourceSafe 6.0. Back in those days, you mention a pull request, and people would probably think you are trying to solicit questionable services/acts. I retroactively learned CVS and Subversion because it was open source (read: free), and hence, preferred by my university’s CompSci department. Outside of the world of academia though, it’s been SourceSafe, followed by TFS. These are centrally managed and were the perfect model for the teams I worked in. Check in, check out, the occasional branch/merge… keeping it simple. Now, slightly alter the code contribution model from 10 people to 100, and it becomes close to impossible to manage the above operations when they need to happen in parallel.
Did your fellow broprogrammer leave for the day? Did you reformat your virtual machine or development workstation? When a file gets checked out in TFS, it gets associated not only to a user, but to his/her workspace (the machine/source code folder they are on). That makes it slightly more difficult to regain access to the file and undo their checkout so that you can take over.
This task is not uncommon and has been blogged about. Huge thanks to Richard Murillo for documenting it in an MSDN blog here: http://blogs.msdn.com/b/rimuri/archive/2006/03/06/544686.aspx
The date of that post is 2006, so here we are 8 years later. Allow me to regurgitate it for you, with full credit to Richard, just in case that post gets removed.
[10:29] New in Windows Azure – Access Control Service, Caching, CDN, Traffic Manager.
We saw Facebook & Twitter icons around ACS. Hopefully, it wasn’t just clipart and they are supported.
[10:26] Umbraco CMS demo. Another .NET based open source project. The twist – running on Windows Azure cloud. Currently used by mainstream sites like vogue.co.uk.
Allows you to scale the instances and looks like it gives you a lot of control on the cloud.
[10:12] Orchard CMS Demo. Open Source project that Microsoft is contributing to. It’s no Sitecore, but still worth taking a look at.