Peter Bengtsson

Looks like a client side error. Me looking into it.

It's probably not a client side error. Loading the pulls takes forever right now https://prs.paas.allizom.org/githubproxy/repos/mozilla/kuma/pulls?state=open

Annoying paas is just failing without any errors or tracebacks. Sigh. The same URLs with the same Github Auth token works locally. I'm going to do a push to see...

Grr.. it's paas being broken again :(

Works for me. I run `npm run run` and then open a browser at http://localhost:3000/ fine. What errors are you getting?

I don't think I understand. If you type in "mozilla" instead of "peterbe" does it not fetch all repos under that organization? Like https://prs.paas.allizom.org/rust-lang for example

> Question - should items cached and invalided by fancy-cache include a `no-cache; no-store` header? Otherwise is there a good way to make sure that the browser doesn't pull a...

It is horribly unprepared for responsive mobile design. I think there are far too many hardcoded widths in the css.

I think if time allowed, I'd like to do the menu, the list of bugs and the main panel thing into three different panels. But how to actually do that...

And, it should use `yaml.safeDump`. So, perhaps to be complete, this should work too: ```javascript const metadata = {match: "!!js/regexp /pattern/gim"} const payload = "Hi there!" const combined = fm.serialize(metadata,...