graphprotocol / graphprotocol/graph-node
[Bug] network not supported by registrar: no network near-testnet found on chain near
Nessuno ha ancora preso questa issue.
- Lingua principale
- Rust
- Stelle
- 3.2k
- Fork
- 1.1k
- Merge medio
- 4g 1h
- PR unite (30g)
- 1
Descrizione
Bug report
Failed to deploy local subgraph, Can you support near local mode?
I'm try to deploy to local subgraph instance use https://github.com/ringecosystem/xapi-offchain/blob/88a75de6c0f1332fa88a762cf0f3907f9b8be931/packages/near-indexer/docker-compose.yml
related:
Relevant log output
# npm run deploy:darwinia -- xapi-near-testnet subgraph.yaml
> @ringdao/xapi-indexer-near@0.0.1 deploy:darwinia
> graph deploy --node https://example.com/training/deploy/ --ipfs https://ipfs.network.thegraph.com xapi-near-testnet subgraph.yaml
› Warning: In next version, we are removing this flag in favor of '--deploy-key'
Which version label to use? (e.g. "v0.0.1"): v0.0.1
Skip migration: Bump mapping apiVersion from 0.0.1 to 0.0.2
Skip migration: Bump mapping apiVersion from 0.0.2 to 0.0.3
Skip migration: Bump mapping apiVersion from 0.0.3 to 0.0.4
Skip migration: Bump mapping apiVersion from 0.0.4 to 0.0.5
Skip migration: Bump mapping apiVersion from 0.0.5 to 0.0.6
Skip migration: Bump manifest specVersion from 0.0.1 to 0.0.2
Skip migration: Bump manifest specVersion from 0.0.2 to 0.0.4
✔ Apply migrations
✔ Load subgraph from subgraph.yaml
Compile data source: receipts => build/receipts/receipts.wasm
✔ Compile subgraph
Copy schema file build/schema.graphql
Write subgraph manifest build/subgraph.yaml
✔ Write compiled subgraph to build/
Add file to IPFS build/schema.graphql
.. QmR95rdKW6dJ31jtWFFQR98zW3wWzzKxnM7evaHFCriK1v
Add file to IPFS build/receipts/receipts.wasm
.. QmYxmWjqpRTnDVRhoXSnQu9nyeT5qWZCtUSAS29Mr4DTet
✔ Upload subgraph to IPFS
Build completed: QmWWcnUXaZMmW4WPvbYL6m6PGuZx9HgFVrDDYySxf3Ht2E
✖ Failed to deploy to Graph node https://example.com/training/deploy/: network not supported by registrar: no network near-testnet found on chain near
UNCAUGHT EXCEPTION: Error: EEXIT: 1
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Riproduci il deployment utilizzando la configurazione linked packages/near-indexer/docker-compose.yml e l’entry point subgraph.yaml, quindi esamina l’errore del registrar per near-testnet. Confronta la configurazione in modalità locale con la documentazione collegata sull’indicizzazione di NEAR e con l’issue correlata #3838. Il lavoro è completato quando un deployment locale di NEAR viene accettato dal registrar senza l’errore unsupported-network segnalato.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust
- Ambito
- backend, blockchain
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100