graphprotocol / graphprotocol/graph-node

[Bug] network not supported by registrar: no network near-testnet found on chain near

Open
#5,690 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Stale
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Description

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:

code: https://github.com/ringecosystem/xapi-offchain/tree/88a75de6c0f1332fa88a762cf0f3907f9b8be931/packages/near-indexer

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the deployment using the linked packages/near-indexer/docker-compose.yml setup and the subgraph.yaml entry point, then inspect the registrar error for near-testnet. Compare the local-mode configuration with the linked NEAR indexing documentation and related issue #3838. Done means a local NEAR deployment is accepted by the registrar without the reported unsupported-network error.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, blockchain
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.