Darkoshi

maybe the view is more than the one table...

2021-02-03T05:57:36Z

The reason why I'm still debugging code at 12:52am is that

I've built a precarious sand castle in my mind
where each grain of sand is a method call or a variable value or some interaction
and if I stop now, the ocean waves will wash the sand castle away,
and I won't be able to get back to it again tomorrow
without having to build it up again from scratch

and anyway, I'm closer now than ever before
at having reached the top of the castle,
so maybe just maybe
the jewel in the upper tower
will be mine
if I reach
a little bit
further

.

achievement reached!
the view is the table
but the 700 table is not the 701 view.
of course, of course!

comments

blankets of white

2021-01-14T08:03:01Z

A layer of fog persisted here past noon today. It felt quiet and muted and calm, like after a snowfall.

An Austrian radio station mentioned a "Schneeflockdown". Schneeflocke is German for 'snowflake'. So Schneeflockdown is a cute bilingual way of saying "snowed in".

.

While debugging, I came across this comment in angular.js:

// Insanity Warning: scope depth-first traversal
// yes, this code is a bit crazy, but it works and we have tests to prove it!

(I didn't write down what version of the file we are using, so am not able to find it online right now.)

This is the code that followed the comment. After that comment, I didn't bother trying to make sense of it. It wasn't related to what I was debugging anyway:

   if (!(next = ((current.$$watchersCount && current.$$childHead) ||
         (current !== target && current.$$nextSibling)))) {
       while (current !== target && !(next = current.$$nextSibling)) {
         current = current.$parent;
       }
     }
   } while ((current = next));

comments

lovely goose chase

2017-03-14T03:49:51Z

I finally figured out that the problem I've been debugging for the last 2 days, was only happening due to me having set a breakpoint in a certain place. One module was writing data to a cache. When another module tried to read the data, it wasn't found. The cache is configured with a "timeToLive" value of 180 seconds (which was unbeknownst to me before, but NOW I KNOW). My breakpoint was causing the data to expire before it could be read, which then caused other errors.

It makes perfect sense now. Back when this problem started happening, it didn't make any sense at all. What I was testing had been working fine before, and then it started getting these strange unexpected errors for no discernible reason.

The ironic part is that I had set the breakpoint in order to change some data on a database row, in order to force an error, as I was trying to test the module's error handling. But then, instead of getting the expected error, I started getting unexpected errors, even when I didn't change the row. At least all this did allow me to find and fix some other problems with the error handling.

comments