deprecated-near-examples / near-pet-shop Goto Github PK

I had a bunch of badly named accounts from testing various things.

They were in my /betanet keystore.

https://github.com/near/near-web3-provider/blob/e88c4f82d2fc04ed33e74c75e2b8c6816e803be1/src/index.js#L385

Seems to load all keys and start calling:

https://github.com/near/near-web3-provider/blob/e88c4f82d2fc04ed33e74c75e2b8c6816e803be1/src/index.js#L390

Which just fails when it encounters a badly named account with this error:

AssertionError [ERR_ASSERTION]: nearAccountToEvmAddress must pass in valid accountID
    at utils.nearAccountToEvmAddress (/home/matt/Projects/near/near-pet-shop/node_modules/near-web3-provider/src/utils.js:294:5)
    at Array.map (<anonymous>)
    at NearProvider.routeEthAccounts (/home/matt/Projects/near/near-pet-shop/node_modules/near-web3-provider/src/index.js:390:38)
Truffle v5.1.57 (core: 5.1.57)
Node v14.15.3

Potential solutions:

• add a helpful (colorful) tip to tell someone to clean up their near-credentials?

• console.warn but don't error?

Typing truffle test yields nothing. CMD just hangs.

I think there's a way to have --network near_betanet be the default so users can just type truffle test and things work.

Is there a reason not to do this?

This section was recently excised in this PR #3 :

Set up trusted relayer

Visit the simple relayer repository and follow directions to run it. This will run a small ExpressJS server locally at port 3000.

Start web app

env NEAR_RELAY_URL=http:127.0.0.1:3000 npm run betanet

This will run a local website. The terminal will display the URL, which is typically:
http://localhost:1234

Once the relayer mentioned gets in better shape let's remember to add this back.