PRs in distress

So here is a new experiment.

Sometimes a PR lingers on too long because the author or maintainer just hasn’t received the help they need. Sometimes it is because a topic expert doesn’t know they are needed, sometimes it is because a PR has slipped through the cracks, sometimes it is hardware, etc… Maybe we can try another thread to connect the right people to the right problem.

I don’t see this as a permanent or even a long term solution (there is quite a bit of discussion going on about getting our tooling connecting the right people to the right problems, that is exciting!), but in the short term maybe this thread can get some PRs merged and encourage people who have had open PRs sitting too long.

So if you have a PR which is stuck, or have seen a PR which is stuck, why not try and post it here. And if you think you can help with a PR that has been posted then you’re awesome!

I’ll start things off with what was originally intended to be a simple update but has been sitting for 4 months because the updated package doesn’t work. The maintainer of the package has been called in but is stumped.

@vaibhavsagar doesn’t have access to a mac so hasn’t been able to resolve some build issues.

@jarjee has been working on some mongodb updates for a while. I think it is pretty important to get these into 19.09 and we’re edging closer to a freeze date. If anyone could help out to ensure newer mongodb versions make it into 19.09 I think that would be great.

Let’s see where this goes I guess.


We could use someone with knowledge about all or any of

  • linux memory overcommit rules
  • cgroups (and how they’re used with the nix daemon)
  • how the java VM claims its memory