Added another lock to the metrics struct to synchronize accesses to the
broker stats. There's a possible race condition if stats are updated at
the same time they are being logged.

We had some data races in the broker that occur when proxies and clients
modify the heap/snowflake map at the same time. This test has a client
and proxy access the broker simultaneously to check for data races.

There's a race condition in the broker where both the proxy and the
client processes try to pop/remove the same snowflake from the heap.
This patch adds synchronization to prevent simultaneous accesses to
snowflakes.

This allows badge and standalone proxies to tell the broker what proxy
type they are.

Proxies now include information about what type they are when they poll
for client offers. The broker saves this information along with
snowflake ids and outputs it on the /debug page.

Trac: 32465

This change makes it easier for us to write tests with mock transports

Also removed some unnecessary code

Switch to containing all communication between the proxy and the broker
in the HTTP response body. This will make things easier if we ever use
something other than HTTP communicate between different actors in the
snowflake system.

Other changes to the protocol are as follows:
- requests are accompanied by a version number so the broker can be
backwards compatable if desired in the future
- all responses are 200 OK unless the request was badly formatted

And simplify EOF check.

Trac: 31028

The variable maxNumClients was unused, while connectionsPerClient was
used for spawning multiple proxyPairs. The former is a more appropriate
name for the multiplexing behaviour we use it for.

Multiplexing now just works thanks to implementing ticket #31310.

Increase readability of code a bit, the function descriptions were
automatically placed in the constructor when we moved from coffeescript.

Use their existence in the proxy pair list to indicate they are active.

We don't need it, and already have a function webrtcIsReady that tells
us what we need to know (whether a datachannel was opened before the
timeout period).

The only place it was used was in window.onpageunload, and we have a
better way of determining if the proxy is active there (through the ui).

I also removed that code from the webextension since the proxy won't
stop running unless you close the browser and after testing it looks
like that code doesn't notify the user anyway.

David Fifield authored 5 years ago and Cecylia Bocovich committed 5 years ago

https://bugs.torproject.org/32129

We haven't implemented SetDeadline for webRTCConn and the error messages
are misleading to proxy-go operators.

Use npm cldr package to get the language name that corresponds to the
country code for the language switcher

- cut down on size of bootstrap.css file
- remove unecessary styles
- fixed typo in javascript comment

Also modified the styling of the page to match the main tp.o page a bit
more

Right now we use the navigator language to determine localization and
replace the website contents with translated strings.

This will make it easier to have translated copies of the site in
subdirectories

Switched to using messages.json for translation strings for
snowflake@tp.o