divma 8fcd22992c No string in slog (#2017) ...

## Issue Addressed

Following slog's documentation, this should help a bit with string allocations. I left it run for two days and mem usage is lower. This is of course anecdotal, but shouldn't harm anyway 

## Proposed Changes

remove `String` creation in logs when possible

2020-11-30 10:33:00 +00:00

..

beacon_chain

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

client

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

eth1

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

eth2_libp2p

No string in slog (#2017)

2020-11-30 10:33:00 +00:00

genesis

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

http_api

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

http_metrics

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

network

No string in slog (#2017)

2020-11-30 10:33:00 +00:00

operation_pool

Update pool/attestations and committees endpoints (#1899)

2020-11-18 23:31:39 +00:00

src

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

store

Disable snappy in LevelDB to fix build issues (#1983)

2020-11-27 03:01:57 +00:00

tests

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

timer

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

websocket_server

Upgrade to tokio 0.3 (#1839)

2020-11-28 05:30:57 +00:00

Cargo.toml

Bump to version v1.0.2 (#2001)

2020-11-28 13:22:37 +00:00