Nick Mathewson authored 6 years ago and David Goulet committed 5 years ago

We had this previously, but we did it differently in different
places. This implementation is pulled from test_prob_distr.c

This reverts commit 387d9448.

This test was disabled in 0.4.0 and later, but the fix in #29298 was only
merged to 0.4.1. So this test will never be re-enabled in 0.4.0.

Part of 29500.

Mike Perry authored 5 years ago and teor committed 5 years ago

Our monotime mocking forces us to call monotime_init() *before* we set the
mocked time value. monotime_init() thus stores the first ratchet value at
whatever the platform is at, and then we set fake mocked time to some later
value.

If monotime_init() gets a value from the host that is greater than what we
choose to mock time at for our unittests, all subsequent monotime_abosolute()
calls return zero, which breaks all unittests that depend on time moving
forward by updating mocked monotime values.

So, we need to adjust our mocked time to take the weird monotime_init() time
into account, when we set fake time.

Mike Perry authored 6 years ago and teor committed 5 years ago

Hopefully this will stop monotime_absolute_usec() from returning 0 on some
platforms in the tests.

Mike Perry authored 6 years ago and teor committed 5 years ago

Cancel the padding timer by changing order of sent vs recv (sent cancels).

Previously we did this for tests only, but it's valuable for getting
proper fork behavior in rand_fast.

Closes ticket 29357, and comes with appropriate notions of caution.

After this fix, we have no more unchecked mkdir() calls.

Bug 29939; CID 144254. Bugfix on 0.2.7.2-alpha.

For scripts that work with python2, use /usr/bin/python.
Otherwise, use /usr/bin/env python3.

Fixes bug 29913; bugfix on 0.2.5.3-alpha.

Having the numbers in those messages makes some of the unit test
unstable, by causing them to depend on the initialization order of
the naming objects.

juga authored 6 years ago and teor committed 6 years ago

When a directory authority is using a bandwidth file to obtain the
bandwidth values that will be included in the next vote, serve this
bandwidth file at /tor/status-vote/next/bandwidth.z.

Part of 29806.

Also fix a grammar error in a comment.

When we clean up, we'd like to clear all the bindings that refer to
a dispatch_t, so that they don't have dangling pointers to it.

This "publish/subscribe" layer sits on top of lib/dispatch, and
tries to provide more type-safety and cross-checking for the
lower-level layer.

Even with this commit, we're still not done: more checking will come
in the next commit, and a set of usability/typesafety macros will
come after.

This module implements a way to send messages from one module to
another, with associated data types.  It does not yet do anything to
ensure that messages are correct, that types match, or that other
forms of consistency are preserved.

Tests included.

We'll be using this for four kinds of identifier in dispatch.c