Lars Eggert
Lars Eggert
This is probably a quant bug in handling flow control updates. Unfortunately, I don't at the moment have the time to look into this.
Still an issue. In case anyone cares.
I think I'm seeing the same issue.
Yes, the org-level `_extends` stuff is broken. See https://github.com/probot/probot/issues/1660 (where nothing seems to be happening...) The QUICWG still has the org-level `.github` repo, but they have also created per-repo configs...
They can be, but by default they are not. We should maybe change the default. Thanks for the tip about yarn/parcel!
> You can run yarn / parcel on the host (it was never disabled). As long as you have node + yarn installed on your machine. Then run `yarn rebuild`,...
Not before next week. IIRC it was something about `gyp`.
Why wouldn't we always provide the full assets image? Manually filling an empty volume and then making sure it doesn't get pruned is way too much work.
How large is the full asset image? Am still unconvinced it would be a problem for GitHub if we just provided that.
Is the full image even 10GB? Also, isn't it possible to keep the rsynced stuff around as a build artifact, so we only need to rsync the diffs for future...