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

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:
        

Problem

isBlockhashValid is a useful RPC call for checking if a transaction needs to be resigned with a new blockhash, but it isn't available in web3.js

Proposed Solution

Add support for it on Connection. More information about the call at https://docs.solana.com/developing/clients/jsonrpc-api#isblockhashvalid

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

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

After X minutes of being open plus Y seconds of idleness (i.e. don't reload while user is moving mouse, etc.), reload the homepage or category pages to show the latest content.

Some unit tests use constructors instead of the block builders, but updating all unit tests is desirable. See nanocurrency/nano-node#2808.

Add custom clj-kondo hooks for macroses to ensure that lint rules are followed inside them.

Macros to be handled:

• fx/defn - similarly to defn with check on metadata for ::events
• fx/merge - seems like it could be lint'ed as thread macro, plus warn on limitations
• defview
• letsubs - lint as let + check on types for

URL

https://app.uniswap.org/#/pool/v2?chain=mainnet

Error

Error: No V2 factory address on this chain

Stacktrace

Error: No V2 factory address on this chain
    at L (https://app.uniswap.org/static/js/main.e43a79ef.chunk.js:1:274135)
    at https://app.uniswap.org/static/js/main.e43a79ef.chunk.js:1:663495
    at Array.map (<anonymous>)
    at https://app

Description

Change links and references in the docs to run an Ethereum node from parity to openethereum, and change these references in the code too.

Motivation

Currently, docs about running an Ethereum node states that you can use parity-ethereum, but the project is no longer maintained.

There's also lots of comments and b

It is currently not possible to specify the chain ID for a hardhat network invoked with npx hardhat node through any means other than the config file. This means it is impossible to specify the --chain-id argument in the command line, or execute a chain host pragmatically with hre.run('node', { chainId: 100 }).

Please add the chainId parameter to the node command so it is possible to

Component

Forge

Describe the feature you would like

When using forge create, if a library is used without being specified in the --libraries param, the following error is produced:

Error: 
   0: Dynamic linking not supported in `create` command - deploy the library contract first, then provide the address to link at compile time

It would be helpful if this message speci

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the