The steps described in our README does not work for me: https://github.com/citusdata/citus/blob/master/CONTRIBUTING.md#following-our-coding-conventions

The main problem is that after cloning the tools repo we need to run make install from top level instead of uncrustify because many of the variables are defined at the top level.

Hi there,

I have a codebase that uses establish_connection. I used Octopus in another (unrelated) part of my app. I did not notice that the parts of the code that used the connection from establish_connection were affected until I shipped to production. After looking through the codebase I realized that octopus_establish_connection actually says I do NOT want to use octopus for this connec

• dble version：
  dble-9.9.9.9-9bf5140bf8483248e94077ba0b429e7d4acfb353-20200326102553
• preconditions ：
  no
• configs：

schema.xml

rule.xml

server.xml

• steps：
  step1. explain information functions in dble such as

explain SELECT ROW_COUNT();

• expect result：
  1. inner_

Description

The REST Api functions have been modified for the network upgrade. Unit tests need to be created to ensure they function as expected.

The new API's are on the v0.2.0 branch.

If anyone wants to pick this up, let me know and I can detail this further.

• Introduce and implement circuit breaker pattern for weaver

Previously we relied on github.com/ethereum/go-ethereum/common package to things like Address.

We need to get rid of this reliance and use our own implementation (especially for our internal/common/address.go). If anything is needed from Ethereum, we need to port their code into our package.

The majority of the prometheus counters are setup, but they aren't being incremented/decremented anywhere (except for slot).

This is a fairly straight forward task, great for exploring the codebase.

recently CI failed many times testing cluster because of port already used, which can be very annoying.

I finished a sqlite version:

from itertools import cycle
from datetime import datetime
import pytz

def create_function_for_sharded_id(shard_id):
    get_next_seq_id = cycle(range(1024))
    og_epoch_datetime = datetime.utcfromtimestamp(0).replace(tzinfo=pytz.utc)

    epoch_datetime = datetime(2016, 10, 19, 17, 54, 24, tzinfo=pytz.UTC)
    epoch_milliseconds = (epoch_dateti

A column needs to be added to explain what operations are required for the parameter items of each xml file to take effect，such as reload? reload-all? or restart dble?