System information

Geth version: 1.10.2-stable
OS & Version: Linux
Commit hash : 97d11b0187b4695ccf44e3b71b54155fe405a36f

Expected behaviour

As mentioned here in the official guide, the following command would allow geth to push metrics data to InfluxDB.

$ geth --metrics --me

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

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

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

Currently release time is manually set by the API. Some third-party applications may not pass this, so we end up in a situation where the various apps have to look at either created time or release time. We also already use this time for sorting.

The solution would be to return created at as the release time when release time is not set

Is it supported at the moment to have 'serialize_as' and 'deserialize_as' on the single field in the sturcture as shown below?

#[derive(Identifiable, Queryable, PartialEq, Debug, Serialize, Deserialize, Insertable)]
#[table_name = "blah"]
pub struct Data {

    #[diesel(serialize_as = "SensitiveStringSerializer")]   
    #[diesel(deserialize_as = "SensitiveStringDeserializer")]

   

Background

Often Tor only nodes become unreachable while still online which causes long channel downtimes and being unable to fulfill Pool bids.

Your environment

• version of lnd
  v0.12.1
• which operating system (uname -a on *Nix)
  Linux raspberrypi 5.10.17-v8+ #1403 SMP PREEMPT Mon Feb 22 11:37:54 GMT 2021
  aarch64 GNU/Linux
• version of btcd, bitcoind, or other back

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

Summary

Include recently added validation fields in validations subscription stream messages:

• version
• cookie
• validated hash

Motivation

This information is useful for server operators, for developing who are putting together dashboards, and the community at large.

ripple/rippled#3291 (comment)

Solution

Modify the <WalletSend> component to allow the user to enter a channel handle and/or LBRY URL to allow sending to, instead of just an address.