Blockchain

System information

Geth
Version: 1.10.13-stable
Git Commit: 7a0c19f813e285516f4b525305fd73b625d2dec8
Architecture: amd64
Go Version: go1.17.3
Operating System: linux
GOPATH=
GOROOT=go

Expected behaviour

Close files that aren't in use / have a settable limit

Actual behaviour

Every database file it opens stays open for the duration of the sync

Steps to re

The backup storage format being defined very simple and dumb, 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

Because header inclusion can be very deeply nested, "using namespace" directive located in header files can unexpectedly change the meaning of the code. It can also lead to the name collision. For instance, it is not possible to define isDigit function in CommonSyntaxTest.cpp.

TODO:

1. Remove [using namespace util;](https://github.com/ethereum/solidity/blob/develop/libsolidity/ast/ASTAnnotatio

When deploying fabric in enterprise's intranet (without the ability to access internet), users maybe upload chaincode builder images and chaincode runtime images to a private docker registry which requires authentication when pulling images.
I think fabric can support this scenario by adding configuration in chaincode section of core.yaml, such as:

chaincode:
    registry:
        

Issue

Currently, in Truffle Contract, you can set numberFormat to "BN" (the default), "String", or "BigNumber" (note this only affects the output; all of these, as well as BigInts, are always supported as input). It occurred to me that we ought to also have "BigInt" (possibly with different capitalization, but I'm sticking to the convention for the existing ones) as a possible `

Diesel currently supports the postgres json and jsonb types. We do not provide built-in support for various operators available for these types. This is a tracking issue for adding support for these operators.

The general strategy for adding support for new operators is as following:

1. Define the operator via [`infix_operator!(

Problem

When booting a node with a clean ledger, the node reports:

[2022-03-01T00:28:52.478485943Z INFO  solana_runtime::snapshot_utils] Purging old snapshot archives in /ledger, retaining 2 full snapshots and 4 incremental snapshots

This is confusing, and suggests that something is wrong. How is the node retaining 2 full snapshots, when none exist?

Proposed Solution

U

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

In the output of list channels the private/public status of the channel is returned, but in the output of pending channels the status is not revealed. To allow for recognizing a pending open channel as a private requires waiting for the channel to confirm.

Ideally the PendingChannelsResponse would include the channel flags or the private/public status of the channel to know which type of chan

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