If we config the cache options in the config file, then it will be overwritten.

We recently took the time to consolidate a number of various implementations of our json-rpc client into a single implementation. The only piece of functionality that's missing in the new implementation is the ability to configure the client to [broadcast a request to N endpoints](https://github.com/diem/diem/blob/master/client/json-rpc/src/async_client/cl

In this error message:

Error: There was a timeout while attempting to connect to the network.
       Check to see that your provider is valid.
       If you have a slow internet connection, try configuring a longer timeout in your Truffle config. Use the networks[networ

After ethereum/solidity#10737 we should be able to replace nearly all non-range-based for loops by range-based loops using appropriate ranges.

Setup

Versions

• Rust: 1.50.0
• Diesel: master
• Database: mysql
• Operating System macOS 11

Feature Flags

• diesel: mysql, r2d2, chrono

Problem Description

The UndecoratedInsertRecord marker [implementation is not included](diesel-rs/diesel@a2996ee#diff-fa14d901408aeec9013f13ab3f012dc

Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

Background

The links to http. proto and annotations. proto no longer exist
Lower versions of GRPC may no longer work with existing code
I cannot access the public IP according to the documentation
Then I upgraded the GRPC to 1.36.0, the os-maven-plugin to 1.6.2, and the protobuf-maven-plugin to 0.6.1, everything was fine

Summary

P2P module should not backoff+retry for connections to peers where there is a chain mismatch, but should expunge the address from the address book and remove it from the list of peers.

Problem Definition

Presently (v0.33; not sure if this is addresses in 0.34), if we connect to a peer on an incorrect chain, the node repeatedly reconnects to this node, and then drops the conn

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

Clients that support multiple server connections would like to have a way to decide which server connection is best able to handle a query. Servers currently "sort of" expose their load as fees, but there's no real exposure of server load in a useful way. Some parameter should be added to the "server" publication stream that clients can just compare across servers to decide which is most likely to