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

Should be done after #12934.

Page

• Cheatsheet

Abstract

When we're done cleaning up the cheatsheet, we could add more interesting information that's already described elsewhere but less concisely. Some ideas:

• Table of available types.
• Various types of literals (in particular string literals like

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

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

Original issue:

diesel-rs/diesel#3032

Relevant PRs:

diesel-rs/diesel#3035
diesel-rs/diesel#3036
diesel-rs/diesel#3037
diesel-rs/diesel#3092

Problem

When using the solana-ledger-tool, the only possible output is plaintext. Example:

> solana-ledger-tool --ledger <my_ledger_dir> bounds
Ledger has data for 2157 slots 131574183 to 131576507
with 1767 rooted slots from 131574183 to 131576250
and 211 slots past the last root

This is fine for human readers, but difficult for machine users.

Proposed Sol

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

Background

Inspired by C-Otto/rebalance-lnd#241.

As part of pathfinding, lnd might encounter edges that have a policy specifying a zero CLTV delta (possibly because of no/outdated gossip?). Every time an edge like this is used in the pathfinding code, a warning is logged: https://github.com/lightningnetwork/lnd/blob/290b78e700021e238f7e6bdce6acc80de8d0a64f/routi

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