I found it! I found the bug!

[mainegreen]

I found the bug in my software code that's been causing problems once or twice a month for over two years!

Dammit, it was *obscure*, all of three lines long but boy, it had some nasty effects like:

* Locking up check runs dumping an obscure error with a message to call the developer
* Magically unpaying a line item here and there, locking it forever in a paid/unpaid state (until I changed it manually)
* Wrecking havok on all financial reports
* Generally leaving me quaking in fear as I ran tests on the database praying that lots of money is still where it should be

I'm gonna have me some frosty beverage tonight!
:bounce:

[spillthebeans]

1. What kind of language? nt

[mainegreen]

3. It's PHP 5.*

unfortunately running against MYSQL 5.0 in the back (I now have a grudge against mysql. It's not very enterprisey!)

[Gormy Cuss]

2. It's the little things....

Here, let's start the celebration now with a few virtual mugs:
:toast:
:toast:
:toast:
:toast:
:toast:
:toast:

[Phentex]

4. Good. That gives you more time to concentrate on our thread.

You know. The Really. Heavily. Viewed. One.

:toast:

[mainegreen]

6. Oi! Thanks for the reminder!

[firefox_fan]

5. Great job!

Bugs can be nasty!

[ZombieNixon]

7. Dude! Me, too!

Today's bug was much easier to track down and fix than yesterday's bug, but it had been irritating me for the past year. One line of code...better yet...one variable. :D

Now yesterday's bug...that was a bitch...now if I only I could get ray intersections to work...:shrug:

Anyway, point is, good job! :toast:

[mainegreen]

8. One variable?

Don't you hate those?

[ZombieNixon]

9. Oh, yes.

Worse yet...it was technically the right variable, it just had the wrong bitshift on it.

It was "statusBits |= (1<<1)" when it should have been "statusBits |= 1" because the respective bits trigger different results. x(

[LynzM]

10. Congrats!!

That's awesome... pour yourself a drink and heave a sigh of relief! :bounce: