部署UNISWAP v3子图到本地图形节点错误:索引句柄inincreaselequipidity#get:带有消息的小数:“ value”不是bigint;

发布于 2025-02-06 15:19:27 字数 1160 浏览 2 评论 0原文

hi,我将此子图将其部署到连接到Goerli网络上局部以太坊节点的本地图节点。

os 是Xubuntu v21.10。

节点是Hyperledger besu v22.1.2。

图形节点版本为0.26.0,并用Docker-Compose运行。

在子图中

  base: 

  block: 

对于部署,我使用以下命令: YARN

纱Codegen

纱线create-local

部署后的部署 - 局部在一些块索引之后,我得到了此错误

ERRO处理程序由于执行故障而跳过,错误:映射在〜 lib/@graphprotocol/graph-ts/index.ts,第811行,第4列,第4列,第4列,带有消息:值不是bigint 。 WASM backtrace:0:0x25f8 - ! src/types/type/schema/token#get:Decimals 1:0x2611-! /strong> 2:0x29e3 - !src/mappings/ 位置 - 经理/处理式的液体,处理程序:handinginCreAseLiquidity,block_hash:0x41EA41EA41EA41EA41EA41EF940B2B057D0F403F403F403F8B2C1C1C32C22C22C22C22C22C2616DD4D4D4D45E0CF3A.7555550.11DC80:numblys:1:1:1:1:1:1:1:numbly _id: QMNWSFK3KJI8ZZMBDVEICGQIORNPYZM1ISTPPVYVNYDSOP,组件:subgraphinstancemanager

与该子图的哪个版本是部署的?

有没有人知道它可以是什么?

Hi, I' m tring to deploy this subgraph to a local graph node that is connected to a local ethereum node on the goerli network.

The OS is xubuntu v21.10 .

The node is hyperledger besu v22.1.2.

The graph-node version is 0.26.0 and run with docker-compose .

In the subgraph.yaml i have removed this:

graft:

  base: 

  block: 

Because i haven't this subgraph deployed local, i changed the network to goerli and the start block to '7011478'.
For the deploy I use these commands:
yarn

yarn codegen

yarn create-local

yarn deploy-local

After deployment and after some blocks have been indexed I get this error:

ERRO Handler skipped due to execution failure, error: Mapping aborted at ~lib/@graphprotocol/graph-ts/index.ts, line 811, column 4, with message: Value is not a BigInt. wasm backtrace: 0: 0x25f8 - !src/types/schema/Token#get:decimals 1: 0x2611 - !~lib/@graphprotocol/graph-ts/index/BigDecimal#constructor 2: 0x29e3 - !src/mappings/
position-manager/handleDecreaseLiquidity , handler: handleIncreaseLiquidity, block_hash: 0x41ea414f5ef6ef940b2b0557d0f403f8b2c1c32c22616dd4d45e0cf3a81dc8d0, block_number: 7011552, sgd: 1, subgraph_id:
QmNwsfk3kJi8zzmBDVEiCGqioRnpyZM1iSTPPVYVNyDsop, component: SubgraphInstanceManager

With which version of graph-node was this subgraph deployed?

Does anyone have any idea what it could be?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

帅冕 2025-02-13 15:19:27

这是您处理程序中的问题。在andledecreaselequidity中检查代码。
看来您的架构中有一个定义为Bigint的字段,但是您正在为处理程序中的该字段分配一个巨大的数字。

如果您发布模式和处理程序代码,则可以进一步调试。

This is an issue in your handler. Check the code in handleDecreaseLiquidity.
It seems like you have a field defined as BigInt in your schema but you are assigning a BigDecimal to that field in your handler.

If you post your schema and handler code it will be possible to debug further.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文