I've been using to last.fm recently and last night had good luck tapping into some great 80's songs by creating a station by using artist: "Kiss". Oddly enough over the course of two hours I didn't hear any Kiss songs but I did venture into a few solo albums from various members of the group. As I was coding away on a personal project, and slightly paying attention to the music, I was brought to full attention when I heard a pretty, Disney, girly, kids' song. What the... When I brought the last.fm window up I was greeted with the meta of the song "A Dream Is a Wish Your Hear Makes" from the "Ultimate Disney Princess"...here's the kicker/defect:

Sang by Cinderella...the late 80's early 90's glam metal band. Hehe, too funny.

Hehe...Funny...'null' is null

Comments are working again. I narrowed it down to the search form I had on this page. For some reason the plain and simple <form></form> tag, using Internet Explorer, and .NET 2.0 causes the following error:

System.ArgumentException: Invalid postback or callback argument. Event validation is enabled using in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
at System.Web.UI.ClientScriptManager.ValidateEvent (String uniqueId, String argument)
at System.Web.UI.Control.ValidateEvent (String uniqueID, String eventArgument)
at System.Web.UI.WebControls.TextBox.LoadPostData (String postDataKey, NameValueCollection postCollection)
at System.Web.UI.WebControls.TextBox.System. Web.UI.IPostBackDataHandler.LoadPostData(String postDataKey, NameValueCollection postCollection)
at System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
while processing http://www1.qainsight.net:8080/login.aspx.

So, for now, no searching from the site. But at least you can comment! You can always search the site using Google though: http://www.google.com/search?q=site%3Aqainsight.net+

I've been avoiding blogging for a while now due to being so frustrated with the comment issue (I probably spent 4 hours, here and there, debugging this thing).  I have a few posts in the queue that will be coming your way soon.

This defect was pointed out by my co-worker and friend Philippe.

Read the ingredients. Chocolate covered SQL anybody?

I'd be interested to know how this came about.

Let's hope that the chocolate is better than the packaging quality control!

Turns out the Blackberry service outage that happended last week was due to insufficient testing of a software update. Oh man, I hate when that happens!

Hopefully lessons were learned by the people at Research in Motion Ltd. Nothing worse than a company that doesn't learn from their mistakes.

Research in Motion, you've used your mulligan.

Today the Portland area was blessed with a fairly decent coating of snow and under that a thin base of ice. With all things coated in white, clean and pretty looking, a defect loomed...

This morning I braved the weather and set out to the streets armed with a 2007 Ford Fusion (front wheel drive with traction control), ice and snow driving skills (which a large amount of Portland motorists don't have), and defensive driving skills taken to the next level (from riding a street motorcycle).

Danger after danger I went around, turned around from & back-tracked, and chuckled at due to the foolishness. My snow-driven cheery mood could not be swayed by danger and foolishness! Two blocks from work I pulled up to the last light that I would encounter on my harrowing journey. With the destination in sight, my mind was at ease and I patiently waited for that green go light. and waited. and waited. AND WAITED.

About 2 minutes into it the lady in the turn lane next to me had enough and started to renegotiate her car's position trying to trip the traffic light's magnetic induction loop inside the road. Watching her, I started to second guess my position since everything was buried in snow. Looked good to me, it all lined up in my mind. Even if we didn't trip the magnetic induction loop, the signal would default to a standard set amount of time per light/direction right? Right!? Wrong. We were screwed. No green for us. Denied by ODOT. Denied by a defect. I can't believe this is the case everywhere, but it sure was at this stoplight.

Three minutes later I looked both ways and went for it. Unscathed I am. Don't try this at home.

I can't imagine this is a feature, so I'll call it my Defect of the Day (imagine loud booming, stereo, monster truck announcer voice with that). Here try it again....DDEEEFECT OF THEEE DAAAAAY:

Many a time while listening to MSN Radio I'll hear a song that I really like and wish that I could hear it again, over and over and over and OVER. Nothing like a little musical spice while testing, spice that forces you to shake your little booty in your chair while nodding your head rapidly to the beat (all the while making darting glances into you rear-view PC mirror to make sure your co-workers aren't mocking you in the background).  Back to the defect... Since its "Radio" you can't rewind or go back right? Wrong...In Media Player (I'm using version 10) when the song is nearing the end press the stop button, the progress indicator will go back to the beginning of the song. Press the play button and the song starts from the beginning. Sweet!

I can't even begin to tell you the number of defects I found today while testing, groovin' with my "MSN Radio manual repeat defect", and Ice Ice Baby.

"Defect of the day" is going to be dubbed "Bug of the day" today and the prestigious award goes out to fellow blogger Dror Engel with this bug found on Google:

Can you spot the defect of the day?

Today's defect is brought to you by Reference.com

The URL to the defect below was emailed to me earlier today. Yes, this is an actual live site. Where do I start?

Can you say "hack me"? This is a security issue (Severity 1). You can't let this stuff bubble up to the user! With the information provided, it wouldn't be too hard to figure out the whole schema and start doing some evil things.

How could they have prevented this? This kind of issue could have been caught with security standards, unit tests, and good ol' functional testing.