Hmm, it looks like I haven't actually merged the "python3" branch into
master which is why a bunch of this looks like I changed it already I
guess ;)
So, see the branch "python3" for fixes to several of the issues you
pointed to. However, there still seem to be some remaining Python3
problems. Al
On Sun, Mar 20, 2016 at 05:18:16PM +, Rusty Bird wrote:
> - moria1 (source 128.31.0.39vs. consensus 128.31.0.34)
> - longclaw (source 199.254.238.52 vs. consensus 199.254.238.53)
Yes, this is intentional.
In the past, this approach has caused governments who tried to censor
connections
Akash Mishra writes:
> I ran all the tests in python3 and generated two new tickets which
> seemed relevant.
Great, thanks!
> However, I am consistently encountering 4 more errors related to
> twisted and zope. I have attached the terminal output with appropriate
> details. Would you be able t
Hi meejah,
Probably the best way to get a feel for what would have to happen to
support txaio (and thus asyncio) would be to take some method that
currently uses @inlineCallbacks and convert it to "just" callbacks +
Deferreds -- as txaio doesn't provide support for @inlineCallbacks /
@corouti
Hi Tim,
>>> But the authority IP addresses hardcoded in the Tor client source code
>>> differ from the authority IP addresses published in the networkstatus
>>> consensus...
>>>
>>> https://github.com/rustybird/corridor/commit/a56d751df399ab1c54f64b0d4dc59f732dc0adc3
>
> Is this still an issue?
>
Hi, all!
I've got a doodle poll open on http://doodle.com/poll/nvx26m4cxspryf3e
to try to find the best time for a network team meeting.
So far, it looks like our options are somewhat constrained, since we
have people who are living from UTC-7 through UTC+11, and a wide range
of time zones in bet
Hi,
I'm trying to figure out why a list from [TorBulkExitList.py] is so much
larger than what is seen in [exit-addresses].
Point in case: Earlier today the list from TorBulkExitList.py contained
58% more addresses than exit-addresses:
--8<---cut here---start->
