How can we identify gerrymandered maps if not by sight? Numerical metrics such as the Polsby–Popper test attempt to measure the “compactness” of an electoral district (the ratio of its area to the square of its perimeter), while the efficiency gap calculates the number of “wasted” votes by computing the proportion of votes that are not used to elect a winner.

If this MR had been merged it would have saved us a lot of time and trouble.

The amount of time wasted on this is ridiculous. Thanks. This is about the only thing that worked. Why in the world this wouldn't "just work" by defining the default url options in Rails config/environments/test.rb is beyond me.

It is also why it's implementation in firefox is completely useless, considering that windows/osx/most linux distros plan to add support for DoH/DoT/DNScrypt resolvers in the near future, so firefox doing it itself will provide no additional benefit.

Unfortunately, it's too late to make the question more specific as this would invalidate some of the (good) answers.

It will be useless work when gvfs-open will solve the bug, but in the meantime...

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

Wasted too much time getting it to work with old Rubies/Rails, when I think the correct path should be to just remove support for them going forward

no one wants to feel like their time is wasted

There is this black hole syndrome where you spend hours working on something and get no feedback.

It seems weird to me that we are trying to enforce commit messages when they are not really visible or used in the GitLab workflow at all. This is what you see most of the time when interacting with the commit list. I've taken time to compose a nice descriptive body and it is hidden by default: