Blockchain

System information

Geth version: 1.9.23
OS & Version: OSX

Feature request

Please add informational metrics to the prometheus endpoint:

• Chain / network info
• Geth version

For example:

# TYPE chain_info gauge
chain_info{chain_id="5", network_name="goerli"} 1
# TYPE geth_info gauge
geth_info{version="1.9.23-stable", arch="amd64", os="darwin", commit="deadbeef", 

The backup storage format being defined very simple and dump, which is expected, there are a few bad cases people need to be careful with.

1. on the backup side, two backup coordinators can run at the same time and write to the storage at the same time, creating duplicate, or even worse, conflicting (if the two coordinators read different chains) backups.
2. on the "read" side, backup CLI tool

OpenZeppelin is currently working on a base-64 library (OpenZeppelin/openzeppelin-contracts#2884) and it turns out that our optimizer is not yet good enough to get to the level of hand-optimized assembly in that case. We should add this code as a test case so that we can use it to evaluate our optimizer improvements.

In the PR and its comments you'll find versions of the

https://github.com/hyperledger/fabric/blob/516bc8bab548a484e2e62fee24b0f4fed5bf6873/core/ledger/kvledger/kv_ledger.go#L542-L547

I'm not sure why this is not implemented the same way as other methods in the same file. If a special case is indeed needed here, some comments would be appreciated

Issue

Vyper handles unmapped instructions differently from Solidity. In Solidity, unmapped instructions are given a file index of -1. When attempting to show the source for such an instruction, we instead just show 1: // No source code found..

However, in Vyper, such instructions are not given a file index of -1, but are given a start and length of 0. So when we show the source for t

Setup

Setup a project with sqlite using the following up.sql:

create table example (
    id integer not null primary key,
    calculated integer generated always as (id*2)
);

Versions

• Rust: 1.56.0 nightly
• Diesel: 1.4.7
• Database: Sqlite
• Operating System Linux

Feature Flags

• diesel: sqlite

Problem Description

Sqlite does

Creating a new issue based on lbryio/lbry-sdk#877

• Update ensure_directory_exists() to check that the directory is writable by the current process.
• If it's not, return a useful error
• Add tests to cover the case when
  • download directory does not exist
  • download dir exists but is not writable
  • dir exists an

Problem

ExecutionTimings are getting a bit unwieldy to maintain.

Proposed Solution

Consider an indexed array structure with common interface for all data points

Background

When doing a closechannel, you need to give a txid and index, separately. Having the option to provide a channel point would be useful.

Marnix
What would be the risk in accepting a chan_point in closechannel? :thinking_face:

guggero
_on the RPC level it's a channel point. so

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

Issue Description

The instructions provided on failed jobs (example) don't clearly explain where to find the generated patch file. This can be a problem for anyone who is not familiar with how Github Actions pages are organized.

The general idea is:

From the details page, click on "Summary", then scroll down to the "Artifacts" secti