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

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

Proposed by @axic in ethereum/solidity#10352 (comment).

Hmm, didn't we also had a sh256 hash next to this? That is way more useful for anyone downloading a static compiler from here and trying to verify it on CI (as that works with shasum -a 256 ).

After doing this the example in solc-bin docs should be updated to include such a hash too.

#2549 introduced the allow_columns_to_appear_in_same_group_by_clause! macro that allows you to use more than one column in your group by clause. It opted not to generate a call to this macro for all columns in the schema via diesel print-schema due to compile time concerns.
I would like to see some experimentation and some concert numbers for the actual compile time impact of this. As I thi

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

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

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