search

tablelandnetwork / js-tableland-cli

Development has moved to: https://github.com/tablelandnetwork/tableland-js/
MIT License
12 stars 2 forks source link

Default provider doesn't work with Infura #1

Open joewagner opened 2 years ago

joewagner commented 2 years ago

https://github.com/tablelandnetwork/js-tableland-cli/blob/c14dc24ba5c97315a464904cee2f963b09f67cdd/src/commands/create.ts#L74

Kuan from Discord was having an issue using Infura. He eventually found a fix by using ethers.providers.InfuraProvider instead of getDefaultProvider

I haven't had a change to debug at all, but wanted to make sure to capture the issue.

joewagner commented 2 years ago

@carsonfarmer I can look into and potentially make a PR if this makes sense to you?

carsonfarmer commented 2 years ago

Hmmm that's a bummer. Ok we might just need to do a 'switch' on the providers and return the appropriate one. So if infura use that, if etherscan use that, etc. Feel free to PR if you have time. Otherwise I'll get to it tonight.

carsonfarmer commented 2 years ago

Fixed with 56ebf7b

andrewxhill commented 1 year ago

hmm seeing this again.

start fresh. tableland init. set pk. set default to maticmum

run tableland create "id int primary key, name text" --prefix "cli_demo_table"

get 

unsupported getDefaultProvider network (operation="getDefaultProvider", network={"chainName":"maticmum","chainId":80001,"contractAddress":"0x4b48841d4b32C4650E4ABc117A03FE8B51f38F68","baseUrl":"https://testnets.tableland.network/api/v1","name":"maticmum"}, code=NETWORK_ERROR, version=providers/5.7.2)

info

tableland --version
5.1.0
➜  ~ node -v
v18.16.0
➜  ~ npm -v
9.5.1

edit: Testing w/ goerli and it works fine. only hit w/ mumbai. i never set my own api key so just using ether's default, if that's the issue we prob need to specify that to a user (which nets wont really be avail unless they set their own api keys/endpoints)