technoweenie's comments

On: KDE is adopting GitLab

[technoweenie]

I just format the message in my text editor and paste it back into the commit message box before submitting.

On: Running GitHub on Rails 6.0

[technoweenie]

> Realistically how many hours of work went into this upgrade process then?

Eileen wrote about the actual process a year ago when GitHub upgraded from Rails 3.2 -> 5.2: https://github.blog/2018-09-28-upgrading-github-from-rails-3...

On: Thundering Herds and Promises

[technoweenie]

FWIW I've always heard it described as a thundering herd. Though, your description is spot on, according to Wikipedia [1]. The problem the article discusses is called a cache stampede or dog pile [2].

[1] https://en.wikipedia.org/wiki/Thundering_herd_problem

[2] https://en.wikipedia.org/wiki/Cache_stampede

I wouldn't fault anyone for getting these similar names mixed up though.

[nitrogen → technoweenie]

It's also possible the Wikipedia article is maintained by someone with a stronger opinion about the definition than would be reflected in the typical person using the term.

[drb91 → nitrogen]

I'd hope so!

On: Thundering Herds and Promises

[technoweenie]

Groupcache is one implementation in Go. However, it uses its own in-memory cache on your app servers instead of an external cache service.

https://github.com/golang/groupcache

https://news.ycombinator.com/item?id=6121501

https://talks.golang.org/2013/oscon-dl.slide#43

On: GoDoc: package letsencrypt

[technoweenie]

We typically run go's built-in server behind nginx. There's no need for something like gunicorn in go.

[jensvdh → technoweenie]

But this would not work in this set-up right? Wouldn't the user facing server (in your case Nginx) have to be the one that serves over HTTPS?

I'm a bit confused about this package.

On: Squash your commits

[technoweenie]

The first time we announced svn support, it WAS a joke: https://github.com/blog/31-back-to-subversion

On: Issue and Pull Request templates

[technoweenie]

GitHub also supports txt and other common document formats: https://github.com/blog/2061-attach-files-to-comments

[shmerl → technoweenie]

Ah, that's a recent addition. Thanks for the pointer. Does it work for bugs? The post mentions pull request comments.

[anonicode → shmerl]

Yes. It works on issues too.

[silverwind → technoweenie]

I wonder why they have restriction based on file extension in place, it's just inconvenient that you have to rename .patch to .txt only for the UI to accept it.

On: GitHub Desktop is now available

[technoweenie]

Here's as close to an official response that I've seen publicly: http://www.quora.com/Why-is-GitHub-for-Mac-not-open-sourced/...

On: Inside GitHub's Super-Lean Management Strategy (20...

[technoweenie]

Correct. Though I wouldn't say the company is any less remote friendly than it used to be.

On: Experimental Dependency Vendoring in Go 1.5

[technoweenie]

How do you handle a custom GOPATH like that when the current repository needs to be in there too? We've tried manually symlinking the repo dir into the custom '$GOPATH/src/github.com/user/repo' dir, but it feels really hacky.

[anezvigin → technoweenie]

You can separate multiple paths with a colon.

[bradfitz → anezvigin]

More specifically, with os.PathListSeparator. (colon on Unix, semicolon on Windows and \x00 on Plan 9)

[lstoll → technoweenie]

We just keep all our go code in one repo.