I had a unclean shutdown less than a day ago and got this warning afterwards:

WARN [03-26|10:10:29.944] Unclean shutdown detected booted=2021-03-17T13:16:42+0000 age=1w1d20h

As it would be better to have the "age=" part closer to the shutdown @holiman suggested to update the marker like every 5 minutes

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.

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.

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

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

Filtering and managing content that Users are interested in is a challenge. I have RSS feed setups that are comfortable and give amazing powers to view/track content that I'm interested in. All the features that are needed is quite extensive, and it will be a challenge to implement.

Setting up an RSS feed for each channel will give the ability to add libry feeds to the same content readers.

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