dpiddy

4 ms·

1. 1.▲
   by dpiddy 4y ago

   You are correct, I should have clarified that it's just the publicly-available tests. Still, those are pretty expansive.
2. 2.▲
   by dpiddy 4y ago

   The bits in https://gitlab.com/cznic/sqlite/-/blob/master/tcl_test.go run the full suite of SQLite TCL tests as part of a Go test. That's in turn run as part a CI setup with results at https:&
3. 3.▲
   by dpiddy 4y ago

   Hey, sorry to hear that. I'm a contributor on the project and if you're able to open an issue ( https://gitlab.com/cznic/sqlite/-/issues/new ) with any info you have it would be very appreciated.
4. 4.▲
   by dpiddy 13y ago

   As discussed on twitter ( https://twitter.com/grittygrease/status/453606054698692608 ), I should have said: We generated new CSRs, with new private keys, but with the same dates and details as the originals. This le
5. 5.▲
   by dpiddy 13y ago

   Hi, Heroku engineer here. We rekeyed our certificates, including the one for *.herokuapp.com, meaning we resent our original certificate requests (CSR) to our CA but signed with new private keys. This is why the dates didn't change. Ou
6. 6.▲
   Using postgression on Travis CI(dpiddy.net)

   4 points by dpiddy 13y ago|0 comments
7. 7.▲
   by dpiddy 16y ago

   Maybe for rubygems, not so easy for apt/rpm as they use gpg signing/verification of package indices.
8. 8.▲
   by dpiddy 18y ago

   woo doggy!