Nick Lincoln
Nick Lincoln
I'm attempting to perform the reverse of #143 In my case I would like to *not* include any fields where the resulting value is missing. ``` using System; using System.Text;...
Currently we define the transaction details (number of, or duration of) by: ``` { label: 'TestLabel0', txNumber: 60, rateControl: { }, workload: { module: 'fabcar/createCar.js' } } ``` it would...
The current logging situation is a little bit ad-hoc. There is no enforced standard, and we would benefit greatly from a serviceability and usability point if we were to enforce...
With refactoring and development work, it is very easy to leave unrequired dependancies in the project. There are tools available such as depcheck https://github.com/depcheck/depcheck that can identify these. Also it...
With the continued evolution of Caliper, it is looking like the current connector lifecycle is not quite right. We should look into updating the lifecycle, taking into account that we...
Current monitor interface would benefit with a `dispose` option so that they can be controlled more
As a caliper user, I would like to access worker metrics, so that I can investigate SDK bottle necks
With the introduction of tx-observers (name pending), we are in the perfect position to enable metric collection on the workers themselves. There are a few implementation routes here, based on...
It is useful to be able to discount initial/final transactions from both transaction and resource statistics. This is because: - certain code types need a "warm up phase" - as...
The Go chaincodes for fixed-asset and fixed-asset-base for fabric are missing the private data methods that currently exist in the nodeJS contract: - add - batch add - get -...
The Java contract for fabric is missing the private data methods that currently exist in the nodeJS contract: - add - batch add - get - batch get In order...