MadLittleMods

Problems with the Go test runner

go test has some bad defaults that have eaten up my time.

Tests suddenly throwing panic: test timed out after 10m0s

Once you've added enough tests to a package, you will magically start to run into the panic: test timed out after 10m0s error. This is because the test -timeout option has a 10m default and the timeout applies on a test package basis, not a per-test basis as you might expect. So when the combined execution time of all tests in the package exceeds the 10-minute limit, this error arises. Diagnosing this issue can be particularly frustrating because each test run takes at least 10 minutes to reproduce and provide feedback. Additionally, the error message makes it seem like it's a single test being the problem, but it's just that one new test that was the straw that broke the camels back and crossed the 10 minute threshold overall.

The timeout mechanism should ideally operate on a per-test basis. If a package-level timeout is still desired, it sh

MadLittleMods

Tried to help someone sign up for their Minnesota (MN) drivers license road test and it was pretty confusing.

Here are some instructions:

1. https://onlineservices.dps.mn.gov/EServices/
2. Appointments -> Schedule an appointment
3. Driver Services -> Class D Skill Exam - First Time (on the next page, it better clarifies this by saying "class D road test")
4. Fill out the form

MadLittleMods

const std = @import("std");

pub fn main() void {
    var list = [_]u8{ 1, 2, 3, 4, 5, 6, 7, 8, 9 };

    // `i = i -% 1` is wrapping subtraction.
    // `i -%= 1`
    var i: u32 = list.len - 1;
    while (i < list.len) : (i -%= 1) {
        std.log.debug("i: {d} list[{d}] -> {d}", .{ i, i, list[i] });

MadLittleMods

const std = @import("std");

// See "a ++ b" in the Zig docs: https://ziglang.org/documentation/master/#Operators
pub fn main() void {
    std.log.debug(
        "We can split up a really long string across multiple lines in Zig using " ++
            "the ++ operator which works on comptime known arrays. Since comptime " ++
            "strings look like `[100:0]const u8` indicating a null terminated array of " ++
            "integers that is 100 characters long, this works just fine.",
        .{},

MadLittleMods

const std = @import("std");
const expect = std.testing.expect;
const expectEqual = std.testing.expectEqual;
const expectEqualSlices = std.testing.expectEqualSlices;

// Tested with Zig 0.11.0
// `zig run x11-flexible-array-member-parsing.zig`

// This is a barebones example from zigx and the code to parse the connection setup buffer,
// https://github.com/marler8997/zigx/blob/a313162bdac3182c7fc38a31dfa952c68ff861f9/x.zig#L2386-L2481

MadLittleMods

10 ns: U U UUU UUU UU
30 ns: U U UUU UUU UU
50 ns: 1 1 000 000 00
70 ns: 1 1 000 000 00
90 ns: 1 1 000 000 00
110 ns: 1 1 000 000 00
130 ns: 1 1 000 000 00
150 ns: 1 1 000 000 00
170 ns: 1 1 000 000 00
190 ns: 1 1 000 000 00

MadLittleMods

Problem

If you have an old version of Hallmark Card Studio and recently upgraded to Windows 10, you might be running into the following error when launching the program. The specific program I ran into this with was Hallmark Home Card Studio version 22/hcs.

A problem was encountered accessing the SQL database. Exception: Unable to load the native components of SQL Server Compact corresponding to the ADO.NET provider of version 8080. Install the correct version of SQL Server Compact. Refer to KB article 974247 for more details

MadLittleMods

Moved to https://ericeastwood.com/blog/convert-an-old-imac-into-a-standalone-monitor/

MadLittleMods

With Red Hat OpenShift, here's how to view logs of a pod in a different project than the one currently active:

oc logs -n <project> <pod>

Option as documented but obscure and hard to follow because the option is namespace but oc always references them as projects everywhere else:

MadLittleMods

Problem

We were dealing with an out of order dump of photos from a Google photos album and wanting to upload to Facebook. It consisted of jpg and heic photos from a iPhone 8 and Pixel 4a so the metadata was different.

Sorting by Date Created in the macOS finder was out of order and Facebook seemed to sort in the same way. It didn't make any sense because we were seeing 4:55am photos sorted below 4:56pm photos (same day). Regardless of Italian timezone, they shouldn't be sorting like that (it's only GMT+2 vs my local GMT-6) which is an 8 hour difference compared the 12 hour difference shown in the photo date/times. Even looking at the exif metadata, it didn't make any sense what it was pulling from to make it sort that way.

Solution

This uses exiftool to read and do the file manipulation.