startBlock lookup does not populate when creating subgraph through graph-cli

Open marcusrein opened this issue 2 years ago • 1 comments

Which packages are impacted by your issue?

@graphprotocol/graph-cli

Describe the issue

When spinning up a new subgraph on a few different verified contracts on Ethereum mainnet, the graph-cli does not populate startBlock during its setup process.

Reproduction

www.thegraph.com

Steps to Reproduce the Bug or Issue

I ran init subgraph deploying through Studio with various smart contracts:

graph init --studio uniswap-token

Entered various smart contracts:

Uniswap Token: 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984 Bored Apes: 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D Cryptopunks: 0xb47e3cd837dDF8e4c57F05d70Ab865de6e193BBB

All were unable to have startBlock populate while spinning up a subgraph.

Expected behavior

I expected startBlock to automatically populate with the location of the smart contracts initial deployment block while spinning up a subgraph.

Screenshots or Videos

Platform

OS: macOS
NodeJS: 19.5.0
@graphprotocol/graph-cli: 0.47.1

Subgraph Manifest

No response

Subgraph GraphQL Schema

No response

Additional context

No response

Apr 25 '23 15:04 marcusrein

Ty, I'll reproduce and see whats going on

Apr 25 '23 15:04 incrypto32