Three bugs in the Go MySQL driver (2020)

One trick to unify the context and io timeouts is roughly:

conn = ...// Wherever you get your file or con.

ctx, cxl = context.WithCancel(ctx)

defer cxl()

go func(){

  defer conn.Close()

  <-ctx.Done()

// Do reads and writes knowing that if your context times out the fd will close and your io op will stop.

The only caveat is if you need to be aware of partial data read/written when a timeout occurs - then you need to tell the os about your timeouts :(.

    defer rows.Close()
    /* do things */
    err = rows.Close()
    if err != nil {
    }

2. If the explicit Close() is never called because of a panic, the deferred Close() will kick in and cleanup the resources.

    func fetchFoo(ctx context.Context) (_ Foo, mErr error) {
        conn := pool.Acquire(ctx)
        defer errs.Capture(&mErr, conn.Close, "close conn for fetch foo")
    }

        defer errs.CaptureLog(logger, conn.Close, "close conn")
        defer errs.CaptureT(t, conn.Close, "close conn")

CI was omni-present on GitHub in the form of Travis; integrating it in GitHub was kind of a no-brainer, and Kanban boards have been around long before GitLab. It seems more "convergent evolution" than anything else.

> incumbent competitor that remained stale for years before being bought by unlimited money Microsoft.

GitHub already got $200-300 million in revenue before they got bought by Microsoft, roughly equal to GitLab today. I don't think money is really the big factor here (and AFAIK GitHub finances are still independent from Microsoft; they don't "pump money" in it).

I don't know why GitHub was relatively stale before Microsoft bought them. I suspect the reasons are more organisational than finance-related.