Whenever I try to install the sinatra gem, the first install hangs during:

"Installing ri documentation for sinatra-2.0.7"

I manually interrupt it, then do it again, and then it works.

I have no idea what causes it, but all the other gems and their ri
documentation do not have this issue.

I believe that there must be something special for sinatra documentation
done that causes this b

The only tests we should be skipping on JRuby are the ones where the feature isn't supported by the platform. I had to add a bunch of skips to get us back to green (skip_on). We should remove these test-by-test.

I'm 99% confident that the problem in all these cases is just racy tests rather than code, but the only way to be sure is a passing test.

As a rack-attack developer
I want the documentation to have a FAQ section
So that we benefit by reducing the chance of duplicated questions in the issue tracker
And users benefit from getting their questions answered faster without the need to wait for someone to answer to their issue

Good source of inspiration could be looking to all past [issues labeled 'questions'](https://github.c

HTTP/2 makes it clear that headers should be lower-case (https://http2.github.io/http2-spec/#rfc.section.8.1.2):

Just as in HTTP/1.x, header field names are strings of ASCII characters that are compared
in a case-insensitive fashion. However, header field names MUST be converted to lowercase
prior to their encoding in HTTP/2. A request or response containing uppercase header field
n

There is a good article about subject: https://developers.facebook.com/docs/facebook-pixel/events-advanced-use-cases/v2.11

It is fairly easy to extend this gem to use pixel with simple events, but what to do with more complex ones, like key stokes or firing pixel on page scroll? Any ideas?

When I printed out page with left-bottom ribbon in development environment, ribbon is middle of page 2.
How about hiding ribbon in css of @media print?

We (GoCardless) run our services in containers, which means a clean file system every time we boot the app.

We should look at what the behaviour is like for people who have file systems that persist between versions of the app. If so, we should look at what mitigations we can implement to make DirectFileStore work by default.

Any edge-cases should be added to the DirectFileStore’s docs.

Stub sets can be managed in a directory unrelated to Stubb using a VCS like Git (branches for sets, commits for undoable temporary changes).

Description

config.ignore_classes should take an array of strings instead of constants (or either?)

Issue

As we add error classes to the ignore_classes we're realizing that we're inadvertently loading those classes that don't need to be loaded. It would be good if ignore_classes can take in an array of class names as strings since this comparison is done at the time of error any

The documentation in the wiki details the NSSwitch extension which should (almost) be considered deprecated: it's incompatible with non-glibc systems (like musl-libc) and with Chrome 41+.

The wiki should document the new dnsmasq configuration, which is more compatible.

refs #9 and #10