Still feeling like shit. To quote a pretty popular movie series, I have a bad feeling about this.
Finding more and more cases where the data from the backend service(s) is nothing short from shit. I am not happy.
@matigo Could be. It is a bit funny that I feel this shitty today when it is my birthday. Some people would find a correlation here, but I don't. I'm just tired.
// @konrad
@matigo I did almost nothing during those 4 days. Well, yes, I did go to the gym and walked a bit, but nothing that could make me feel this shitty. Yes, I did walk ~3 km to a hardware store in a snowstorm yesterday, but that was not a major exhaustive exercise.
// @konrad
Oh, and happy birthday @matigo! I hope you don't feel as old as I do1 today.
Even though you are older than me. ?
Even though I was able to relax and rest the whole 4-day weekend, today I feel like I am run over by a steam roller.
I take that back a bit. The database read fails to acquire the lock even though the write (in another thread) does release it. The reads in the writing thread do work (because they are in the same thread, as per the lock design) as do the reads in the UI thread. But in this one particular thread the read fails. Grr…
Today’s Android headaches: multithreaded database access and some weirdness with asynchoronous tasks.
In the former, a lock-controlled read from the database gets stuck because some other operation (which one, I have no idea, all the other locked reads and writes should have been ready by that) has not released the lock. In the latter, an AsyncTask that (supposedly) should perform its operations in a certain order (pre-execute in the calling thread, the actual task in a background thread, and post-execute again in the calling thread) calls them in the wrong order (in this case, the pre-execute after post-execute).
Now, where did we put our booze…