query execution failed: Subgraph has not started syncing yet.

日志里已经开始块同步了 但是查不到在这里插入图片描述
在这里插入图片描述
本来感觉[0,0]不对
但是找到了这个说是对的 https://docs.skale.network/develop/using-graph
在这里插入图片描述
docker-compose logs -f | grep Scanning
查看一下同步的日志
在这里插入图片描述
明明有同步,却还是查不到数据

------------------------分割线-------------------------------------------------

兄弟们我成功了!!! 事实证明不是部署上的错误,是我选用的链的RPC节点不行!而且[0,0]是不对的!应该是增长的。
经过几次略微调整我认为可能不对的点,重新部署之前的rangers链后,还是不对 !
于是我决定换条链试试,我把合约部署在了 rinkeby测试网,节点选用infura的,
在这里插入图片描述
在这里插入图片描述

https://rinkeby.infura.io/v3/<your infura api key>

然后还是按着上篇文章的步骤进行了部署,但是thegraph节点,不用重新部署了,直接

docker-compose down
vim docker-compose.yml
(修改这行:ethereum: 'rinkeby:https://rinkeby.infura.io/v3/<your infura api key>')
docker-compose up -d

然后参考上篇将子图部署到私有节点上。

graph-node_1  | Sep 22 08:19:00.563 INFO Received subgraph_deploy request, params: SubgraphDeployParams { name: SubgraphName("MetaverseMan/Game"), ipfs_hash: DeploymentHash("QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F"), node_id: None, debug_fork: None }, component: JsonRpcServer
graph-node_1  | Sep 22 08:19:05.581 INFO Resolve schema, link: /ipfs/QmdKLtNAeVDpuKL1yYEQHn7Bdh7iqjbVHtsgwHL9GTobBu, sgd: 0, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphRegistrar
graph-node_1  | Sep 22 08:19:05.582 INFO Resolve data source, source_start_block: 0, source_address: Some(0xc716e9df2bb6b6b5b3660f4d210d222e952abfce), name: Game, sgd: 0, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphRegistrar
graph-node_1  | Sep 22 08:19:05.583 INFO Resolve mapping, link: /ipfs/QmcmqtAfWdyR2ZdtmpEKtRQDwzrCPw7U2c8woJyZad7b3P, sgd: 0, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphRegistrar
graph-node_1  | Sep 22 08:19:05.583 INFO Resolve ABI, link: /ipfs/QmapPy7RyHEGVX7Fpp8ZgjdeeDXGN3JA2xnvJzbV78R2rP, name: Game, sgd: 0, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphRegistrar
graph-node_1  | Sep 22 08:19:05.594 INFO Set subgraph start block, block: None, sgd: 0, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphRegistrar
graph-node_1  | Sep 22 08:19:05.594 INFO Graft base, block: None, base: None, sgd: 0, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphRegistrar
graph-node_1  | Sep 22 08:19:06.255 INFO Starting subgraph writer, queue_size: 5, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.266 INFO Resolve subgraph files using IPFS, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.266 INFO Resolve schema, link: /ipfs/QmdKLtNAeVDpuKL1yYEQHn7Bdh7iqjbVHtsgwHL9GTobBu, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.266 INFO Resolve data source, source_start_block: 0, source_address: Some(0xc716e9df2bb6b6b5b3660f4d210d222e952abfce), name: Game, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.267 INFO Resolve mapping, link: /ipfs/QmcmqtAfWdyR2ZdtmpEKtRQDwzrCPw7U2c8woJyZad7b3P, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.267 INFO Resolve ABI, link: /ipfs/QmapPy7RyHEGVX7Fpp8ZgjdeeDXGN3JA2xnvJzbV78R2rP, name: Game, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.268 INFO Successfully resolved subgraph files using IPFS, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.268 INFO Data source count at start: 1, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: SubgraphInstanceManager
graph-node_1  | Sep 22 08:19:06.520 INFO Scanning blocks [0, 0], range_size: 1, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:07.216 INFO Scanning blocks [1, 10], range_size: 10, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:07.915 INFO Scanning blocks [11, 110], range_size: 100, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:08.605 INFO Scanning blocks [111, 1110], range_size: 1000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:09.310 INFO Scanning blocks [1111, 3110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:10.000 INFO Scanning blocks [3111, 5110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:10.763 INFO Scanning blocks [5111, 7110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:11.463 INFO Scanning blocks [7111, 9110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:12.190 INFO Scanning blocks [9111, 11110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:12.900 INFO Scanning blocks [11111, 13110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:13.603 INFO Scanning blocks [13111, 15110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream
graph-node_1  | Sep 22 08:19:14.296 INFO Scanning blocks [15111, 17110], range_size: 2000, sgd: 1, subgraph_id: QmaKiVgqUe29bhNm8ZJ5EpbosyjaTNQBaKH9hMmrXjeV5F, component: BlockStream

看到扫块的个数是增长的,不是[0,0]…这里也被那篇文章误导了,以为[0,0]是正常状态,其实用菊花想也应该是有增长的。
这个时候再去面板查询就已经不是query execution failed: Subgraph has not started syncing yet 了,而是正常的展示,没报错。
现在还没同步完,我的合约在11423609块上,目前看还得同步个个把小时。一会好了查查看。对了,这个scanning是从0块开始扫的,syncing是从你部署的时候的高度开始同步的。
在这里插入图片描述
----------------------------------分割线---------------------------
在这里插入图片描述
同步完了。查询功能正常使用。

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Template execution failed: ReferenceError: document is not defined 这个错误表明在模板执行过程中发生了一个错误,错误信息为document is not defined。这个错误通常是由于在代码中尝试使用document对象,但是在当前的上下文中没有定义document对象所致。 根据提供的信息,可以看出你的错误可能与webpack打包配置有关。在你的index.html文件中,有一个<link rel="icon" href="<%=htmlWebpackPlugin.options.url%>favicon.ico"></link>的代码段,该代码段可能会尝试使用document对象。然而,由于webpack的打包过程中,document对象可能无法在服务器端运行时使用。这可能是导致错误的原因之一。 此外,还有一个<script src=<%= BASE_URL %>/tinymce4.7.***由于webpack的打包过程中,这段代码也可能无法正确执行。 要解决这个问题,你可以尝试将涉及到document对象的代码从模板中移出,并放置到适当的位置。你可以将这些代码放在适当的生命周期钩子函数中,例如在Vue组件的mounted钩子函数中。这样可以确保在浏览器环境中执行这些代码时,document对象已经定义好了。同时,你也可以使用Webpack的插件或者loader来处理这些特定的代码段,以适应打包的环境。具体的配置可以根据你的需求和项目的特点来确定。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* [打包报错ERROR in Template execution failed: ReferenceError: BASE_URL is not defined](https://blog.csdn.net/a1783118/article/details/131432872)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 50%"] - *2* *3* [Template execution failed: ReferenceError: htmlWebpackPlugin is not defined](https://blog.csdn.net/zyj24685144/article/details/116303942)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值