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 doing division and modulo operation with constant or immutable denominator it is possible to only do compile-time denominator check and skip runtime checks.

Consider following contracts:

pragma solidity 0.8.15;

uint256 constant _MODULE = 17;

contract C1 {
    function f(uint256 a) external pure returns(uint256) {
        return a % _MODULE;
    }
}

contract C2 

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

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:
        

• I've opened a support ticket before filing this issue.

Issue

Tests are not isolated from each other. I reproduced it using the metacoin box tutorial, adding a new test at the end that checks again the balance. As per the "clean-room" the first account should have all 10000 tokens. It's not.

Problem

Loss and latency metrics might be interesting from the gossip ping-pong protocol.

Proposed Solution

Capture and report them.

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

The fuzz tests we have don't run on my machine anymore with go1.18. dvyukov/go-fuzz is basically deprecated at this point. We should upgrade to language-native testing.F even if it's not that great yet.

Basically the fuzz tests should stay the same, but the build step is changed:

• remove make-level fuzz references
• fuzz tests that don't need to import from other packages can live in

In working on informalsystems/tendermint-rs#1144, I see that the statesync.fetchers configuration option is serialized as a string. Does it need to be a string? It seems like it should be an integer value.

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

The custom parseUrl() implementation contains a potential edge case issue regarding the parsing of ports.

Consider the following group in the regular expression that determines basic acceptance of the URL: StringUtilities.cpp#L61-L62

 // optional port