Blockchain

Compilation errors due to change in Azure library "github.com/Azure/azure-storage-blob-go/azblob"

In /build/ci.go : func doPurge()

Line 1241: blobs[i].Name undefined (type invalid type has no field or method Name)

In /internal/build/azure.go

line 73: BlobItem not declared by package

And others ....

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

Apparently we have the assert macro disabled in CI, even in non-release builds - at least on Windows (see ethereum/solidity#12634 (comment)). While this macro is generally discouraged in our project in favor of the solAssert() family of macros, we still do have them in some places and I think that they should

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

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

SystemInstructions link on the Solana Docs does not work with version 1.9.9.

Leads to:

![Screenshot 2022-02-24 at 18 42 05](https://user-images.githubusercontent.com

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