Hi there!
I am Sreenatha(lucyd). I am interested in working on Tor Weather this
summer as a part of GSoC 2014.
I helped Damian migrate weather to stem(#8264) last summer and have been
following the work on it's rewrite. I made an attempt to further this by
writing
a couple of python scripts.
1.
"Nick Mathewson" wrote:
I assume this test works on Linux where AFAICS malloc() returns a buffer
with zeros. If so, shouldn't calloc() be used in 'setup_data_buffer()'
instead?
The test is broken: it doesn't work on any platform. Look how buffer2
was copied directly from buffer1: they can't
Hi Tor Devs,
I'm a computer engineering undergrad at University of Illinois
Urbana-Champaign. I am interested in working on a GSoC pluggable transports
project.
I mainly code in python or common lisp and have worked with asynchronous
programming before (albeit it was a java framework not twisted).
On Fri, Mar 14, 2014 at 6:31 AM, Gisle Vanem wrote:
> Since tinytest_demo.c now calls Sleep(), we must include .
Looks good; applied it.
FWIW, tinytest is a slightly independent project; it's on github at
https://github.com/nmathewson/tinytest .
___
to
On Fri, Mar 14, 2014 at 6:53 AM, Gisle Vanem wrote:
> The 'test_memcpy()' in tinytest_demo.c assumes there is a NUL in one of the
> buffers. (the comment says so). That's not the case here on Windows. At
> least not in MSVC debug-mode where malloc'ed buffers are filled with '0xCD'.
> A snippet fro
The 'test_memcpy()' in tinytest_demo.c assumes
there is a NUL in one of the buffers. (the comment says so). That's
not the case here on Windows. At least not in MSVC debug-mode
where malloc'ed buffers are filled with '0xCD'. A snippet from my output:
../ext/tinytest_demo.c:159: assert(db->buff
Since tinytest_demo.c now calls Sleep(), we must include .
Patch:
--- Git-latest/src/ext/tinytest_demo.c 2014-03-13 20:44:56 +
+++ src/ext/tinytest_demo.c 2014-03-14 11:21:56 +
@@ -36,7 +36,10 @@
#include
#include
#include
-#ifndef _WIN32
+
+#ifdef _WIN32
+#include
+#else
#includ
Hi devs,
we had an IRC meeting last week, on March 7, to discuss next steps for
the Tor Instant Messaging Bundle (TIMB). At the end of that meeting we
decided to have another meeting 1 week later, so today.
However, there will be no such meeting today!
The main reason for today's meeting was to
