In order to perform refactoring and to add new features with more confidence, we need unit, integration and end-to-end tests for:

• algorithm parts. Seesrc/algorithms

• React parts - components and pages. See src/components and src/pages

• State management: redux reducers and sagas. See src/state

The infrastructure:

• jest and @testing-libraryare already set up. Un

Overview

As a developer/admin user, I would like to create a smart contract management suite to deploy, manage and update Baseline (as modeled in Radish34) smart contracts to the mainnet

Reference

• EIP1077
• Upgradable Contracts

Questions

• What are t

Mainly due to defaulting of .any.js and not inserting the necessary boilerplate.

There are some interesting algorithms in simulation from Physics, Chemistry, and Engineering especially regarding Monte Carlo simulation: Heat Bath algorithm, Metro-Police algorithm, Markov Chain Monte Carlo, etc.

Having a value:

rapidjosn::Value value(1);

and a schema:

{
    "allOf": [
        { "type": "string" },
        { "type": "string", "minLength": 2 },
        { "type": "string", "pattern": "^z" }
    ]
}

rapidjson::SchemaValidator gives an error object:

{
  "type": [
    {
      "expected": [
        "string"
      ],
      "actual": "integer",
    

What problem does this feature solve?

Letting devs know which Node version to use for dev and tests.
When contributors first clone the repo and run $ yarn, they might not have read CONTRIBUTING.md yet where it says Node 10 .

What does the proposed API look like?

1. Something like package.devEngines that React uses to enforce via [installation hook](https://github.com/facebook/f

I don't know if this is the right repo to suggest an improvement on jitsi.org; but given the really exceptional experience provided by the installer I suggest the following additions to the "Ubuntu / Debian Installation Instructions" at https://jitsi.org/downloads/ubuntu-debian-installations-instructions/

• add instruction on how to generate a lets encrypt certificate
  /usr/share/jitsi

Like dotnet build, printing the total runtime would be good for diagnostics.