Just finished fighting with a Linux server that somehow ended up re-activating a service which it didn’t need, but which interferes with a service that it does need. *grumble*.
Boss returned this morning from a week out following back surgery…and has jury duty. Figures if he actually gets called in, he can easily get it dismissed, but for now, the only number he has is for the automated message.
Managed to mostly avoid fire+smoke problems this weekend, except Sunday afternoon why my eyes just wouldn’t stop itching. A co-worker had to evacuate his parents from Yorba Linda on Saturday, but their house made it through okay.
Got together with andrea_wot, wayens and gasean for Andrea’s birthday and monopolized a table at Cosi for about 4 hours on Sunday. Fortunately they didn’t seem to mind!
Caught up on comics & Netflix over the weekend. Read Crecy, about the 1300s battle in which the English longbow triumphed over vastly superior French numbers. Mostly about medieval war tactics, swearing, and xenophobia. Narrated by an utter bastard who breaks the fourth wall a lot. Did I mention it was by Warren Ellis? Also read Chrono Mechanics, about a squad of techs whose job is to repair time. A bit too crazy even for me, and I loved Tales from the Bully Pulpit. And finally Harley and Ivy, a collection of stories focusing on Batman villains Harley Quinn and Poison Ivy, which was great fun.
As for TV, we’ve finished season 1 of Tsubasa: Reservoir Chronicle. I also wrapped up watching season 5 of The Batman (though I haven’t watched the earlier seasons, and based on this one, probably won’t). And then there’s Stan Lee’s Lightspeed…I had to watch it because it’s about a speedster, but OMG it was awful. At least now I know Netflix’ "Watch Instantly" service works well with our system/connection. Snarky commentary will go up at Speed Force in the next week or two.
We’ve backed off on the house hunting for a bit. We actually got a counteroffer on one of the places we looked at a few weeks ago, but decided not to take it. We need to reevaluate what we’re looking for before we dive back in.
Drove alenxa to an interview this morning. Thought it was in one of those two new buildings by the spectrum until she told me the address, and realized it was actually across the street from where I work. Highly convenient for today, but the actual job location is off in another direction.
Well, the bugs just fly. After leaving the scene with you going to your server, I got a call and had to go back to my app. Web application came across error message preventing use… But when I got there, checked on the thing, confirmed the error message, got ready to debug, and went for a first pass…
It came up fine…
wtf?
lol At least I got some work done while waiting for the thing to load and for the users overseas to get back to me on the thankful but puzzling results.
Needless to say, arrived home late. ;p
Ugh… did I ever mention the bug I had to track down that would only occur on release builds, and never on debug builds? It turned out to be an uninitialized variable that, for some reason, got initialized anyway when the program was compiled for debugging. (Go Visual Studio.) So I could either reproduce the bug without being able to step into the code, or step into the code without being able to reproduce the bug.