Michael Kernaghan

this has been fixed

We will want the test app to show the version of Taquito code it is running

I have converted the list of RPC nodes to a table and added a link to check the node is up. The live link to show level and protocol still...

Tezos Doc on Flexible Network Sandboxes. https://tezos.gitlab.io/developer/flextesa.html

I tried a few things first, set up sandbox: https://assets.tqtezos.com/docs/setup/2-sandbox/ then: in integration-tests/package.json add to scripts { ` "test:sandbox": "SANDBOX=true jest",` in integration-tests/config.ts add: ``` const sandboxEphemeral = { rpc:...

I have attached a list of all the contracts that are used in the integration tests [Contract-ids-used-in-integration-tests.txt](https://github.com/ecadlabs/taquito/files/6157573/Contract-ids-used-in-integration-tests.txt) Perhaps only the "known contracts" are required. These are just: ``` ~/taquito/integration-tests/config.ts 61,19:...

Steps: 1. Deploy flextesa sandbox onto a virtual machine and get the node running - done 2. Run the deploy-integration-tests-contracts.ts script to populate the sandbox - script times out 2021-03-18...

Here is the error when I run the Taquito script to create bigMap assets on the sandbox on the VM: (deploy-integration-tests-contracts.ts) ``` mike@halen:~/taquito/example$ node -r ts-node/register deploy-integration-tests-contracts.ts Deploying the knownContract......

We have lowered the polling time to no effect `tezos.setProvider({config: {confirmationPollingIntervalSecond: 1}})`

Closing this as the decision has been taken to not fully support all the L2 things. Other issues capture what will be changed.