Freedom! Sweet, delicious freedom! I went dark since March for crunch time at Amazon, but then decided one decade there was enough. Amazon was a great first job but time for a break.
Vacation aside, this summer I’m volunteering with our island food bank and Granny’s Attic to get more balance away from the keyboard. That said, knowing myself I’ll still need my open source fix.
Oh! And of course, most important of all: found a new puffy friend!
Damn I’m a sucker for puffers.
Tor/Stem CI
Stem’s tests were designed to verify Tor/Stem’s interoperability, as well as provide a tool to test Tor itself. This month teor integrated Stem into Tor’s Travis CI and we’ve been working out the kinks…
- Added support for multiple ‘–test’ arguments so CI can limit testing to interoperability, speeding CI and reducing false positives. (#30653)
- Added a ‘–log-file’ argument so logging can be directed to a file rather than stdout. (#30675)
- Emitting tracebacks in response to SIGABRT and SIGUSR1 signals. (#30012, #30122)
- Fixed test hangs that were caused by sandtraps on tor26 and Serge’s DirPorts.
- Emptying tor’s data directory between runs and raised tor’s log runlevel. (#30592)
- Corrected test failures. Couple were related to Tor (#30746, #30697), but most were on Stem’s side (#30696, #30597, #30598).
Smaller things these last few months include…
- Bandwidth file v1.4 header support. (#30160)
- Bandwidth files can now be downloaded through the stem.descriptor.remote module. (#26902)
- Improved tor-prompt’s performance by ~34%. (#28300)
- Cleaned up no-op escape sequences. (#27270)
- Tor’s bandwidth-file-headers descriptor field was misordered. (#30282 and #30316)
- Exit policies were not thread safe. (#29899)