Re: [tor-relays] Tor t-shirts

2017-10-21 Thread Iain R. Learmonth
Hi, On 21/10/17 09:06, Roger Dingledine wrote: > That said, the folks handling tshirt requests are the real arbiters > of how they are interpreting my sentences, so I will defer to them. :) I was sure we had a bug for this, but I can't find it. Here's a bug I just filed to include eligibility

Re: [tor-relays] Tor 0.3.1.7 - bug report

2017-10-21 Thread diffusae
Thanks a lot for your hint. On 21.10.2017 12:45, Alexander Dietrich wrote: > Sounds like bug #23551 > (https://trac.torproject.org/projects/tor/ticket/23551), which will > apparently get a fix on 0.3.1. Yes, it really looks like that. Seems to be zstd version incompatibility. I discovered it

Re: [tor-relays] Tor 0.3.1.7 - bug report

2017-10-21 Thread Alexander Dietrich
On 2017-10-21 01:25, diffusae wrote: Oct 21 01:09:10.000 [warn] tor_bug_occurred_: Bug: src/common/compress.c:576: tor_compress_process: Non-fatal assertion !((rv == TOR_COMPRESS_OK) && *in_len == in_len_orig && *out_len == out_len_orig) failed. (on Tor 0.3.1.7 6babd3d9ba9318b3) Oct 21

Re: [tor-relays] Tor t-shirts

2017-10-21 Thread Roger Dingledine
On Sat, Oct 21, 2017 at 12:28:34AM +0100, Dylan Issa wrote: > To add on this, if my Tor relay was restarted for a reason (resets downtime) > but previously had ~50 days uptime, if I get the remaining 10 days am I > eligible? Or must it be at least 60 days of continuous uptime? > Because I had 50

Re: [tor-relays] "Removed 1565259696 bytes by killing 1 circuits"

2017-10-21 Thread Roger Dingledine
On Fri, Oct 20, 2017 at 07:27:22PM -0400, tor wrote: > In a relay's logs: > > Oct 20 10:31:47 X Tor[]: We're low on memory. Killing circuits with > over-long queues. (This behavior is controlled by MaxMemInQueues.) > Oct 20 10:32:11 X Tor[]: Removed 1565259696 bytes by killing 1