- User Since
- Sep 7 2015, 3:25 PM (214 w, 1 d)
Mon, Oct 14
I'm a bit worried that this pulls http and https from the same set of files without distinction; This looks like a good catalyst for subtle single-character bugs.
Fri, Oct 11
Tue, Oct 8
While I understand what the fixture does, its documentation is lacking (you're only really documenting the inner callback, that users won't call into, not the fixture itself). I guess most of the documentation of the callback should move to the fixture itself?
Mon, Oct 7
Pluggable compression has been implemented for all objstorage backends, which means we could
- store the (compressed) bundles in an uncompressed objstorage on azure
- when a user requests the bundle
- generate a temporary URL (using BlobSharedAccessSignature.generate_blob)
- redirect to that temporary URL
Fri, Oct 4
Thu, Oct 3
The aforementioned cards have been received, installed and zfs has been setup to use them.
There was a bug in the (manually modified) Let's Encrypt config for this domain, which was silently ignored by certbot (nice), and prevented the renewal to trickle down to puppet.
Wed, Oct 2
Tue, Oct 1
♪┏(・o･)┛♪┗ ( ･o･) ┓♪ do the rebase dance party
Mark race condition test as xfail
Sounds like a good first fix, thanks.
Would it be possible to make that extra dependency on dulwich optional, e.g. only installed when requesting swh.model[identify]?
I've rebased the jdk11 image on top of buster using the awful, awful a3776d744f. This means python 3.7 by default, and it looks like swh.graph CI works.
Switch conditions to get a ==