Attila Klenik, PhD

In the `encodeSingle` function, addresses are [translated](https://github.com/ethereumjs/ethereumjs-abi/blob/572d4bafe08a8a231137e1f9daeb0f8a23f197d2/lib/index.js#L117) to `unit160`, so far so good. Then the recursive call hits the [uint-like check](https://github.com/ethereumjs/ethereumjs-abi/blob/572d4bafe08a8a231137e1f9daeb0f8a23f197d2/lib/index.js#L162) and the supplied size (i.e., 160) is retrieved. However,...

Fabric contract deployment silently fails in generator CI test

1

## Context The Fabric contract deployment benchmark phase silently fails in the generator CI test: https://dev.azure.com/Hyperledger/Caliper/_build/results?buildId=43967&view=logs&j=e6706e9b-7179-5ea0-f5f6-2478cba53eeb&t=f8516254-b8a4-5110-1a40-195a342bbf75&l=344 The serious problems are that: 1. No error is logged to indicate what happens...

Add skeleton for development and proposal docs

2

Draft PR showcasing the envisioned structure of the dev docs. Signed-off-by: Attila Klenik

The agreed-upon naming convention is `Resource Monitor` (in the manager) and `Transaction Monitor` (in the workers). Currently, the `Observer` naming is used for TX monitors, which is confusing since we...

### Please share the technical limitation of Caliper that you encountered. The data provided by the declarative workload module only contains the parameter names and values: https://github.com/hyperledger/caliper/blob/f0553d1bf05711a671db99af0704c5e1b5fb816d/packages/caliper-core/lib/worker/workload/declarative/declarative-workload-module-base.js#L73 More information is...

### Please share the technical limitation of Caliper that you encountered. Caliper workers call workload modules either for a specific number of transactions or a fixed duration. However, benchmarks containing...

### Please share the technical limitation of Caliper that you encountered. Workload modules of different rounds and workers require some common data to be shared (e.g., a common seed for...

### Please share the technical limitation of Caliper that you encountered. Caliper uses the same constant number of workers for each round. This complicates the implementation of "initialization workloads" that...

## Context If every winston transport is "above" a certain log level, then messages up to that level should not be processed. ## Expected Behavior For example, if every transport...

The license checking mechanism present in the Caliper repo should also be added to this one, enforced by a simple Travis job.