graph-tooling
graph-tooling copied to clipboard
Monorepo for various tools used by subgraph developers.
In https://github.com/graphprotocol/graph-tooling/pull/1204 we moved a lot go subgraph examples, it would be great if we can have tests for all of them that runs in CI
Today we have a [map that we maintain](https://github.com/graphprotocol/graph-tooling/blob/main/packages/cli/src/codegen/types/conversions.ts) to convert between ABI, Assembly Script and that is what is what we simply use to [map to GraphQL Types](https://github.com/graphprotocol/graph-tooling/blob/2efea49f1e6344518ea47e98b572ae8dbdc506f6/packages/cli/src/scaffold/schema.ts#L17-L20). This approach...
while working on https://github.com/graphprotocol/graph-tooling/pull/1201 it isn't very simple to repro and debug the issues. Would be great if we can have a unit tests and e2e test suite.
### Which packages are impacted by your issue? @graphprotocol/graph-cli ### Describe the issue Currently, there is almost no possibility to know which exact source was compiled into the WASM binary...
Hi all, I believe this is due to the `sync-rpc` dependency attempting to load a local webserver at require time, although I'll admit I've not done the full stack crawl...
## What If an output value of an event is int256, it may not be displayed correctly in subgraph. I would like to know how to solve this problem. ##...
Hey all! So I am trying to make a contract call to a solidity method in the Wyvern OpenSea exchange contract. I've linked a gist explaining where I think the...
I have the following bytecode which is an input of the following [tx](https://goerli.etherscan.io/tx/0x181e8f98b3a78c59114d1931cd7d3be7fd201a530d4be34068117102ebd2f1f8) ``` 0x1fad948c0000000000000000000000000000000000000000000000000000000000000040000000000000000000000000dbd510f9ebb7a81209fccd12a56f6c6354aa8cab000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000200000000000000000000000003ba340bc4194d7315c6f9f19aabc5f4a5cdc2e220000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000001a000000000000000000000000000000000000000000000000000000000000493e0000000000000000000000000000000000000000000000000000000000003d0900000000000000000000000000000000000000000000000000000000000005d7000000000000000000000000000000000000000000000000000000000597771400000000000000000000000000000000000000000000000000000000059682f0000000000000000000000000000000000000000000000000000000000000004a000000000000000000000000000000000000000000000000000000000000005600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002c4f34308ef00000000000000000000000040a2accbd92bca938b02010e17a5b8929b49130d000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001a48d80ff0a00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000152007ddefa2f027691116d0a7aa6418246622d70b12a00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044095ea7b3000000000000000000000000a275da33fe068cd62510b8e3af7818ede891cdff0000000000000000000000000000000000000000000000000005b7e11a47f000000014f33fc01017d9ac6762e8285b51ad07089e51000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000649b890b700000000000000000000000003ba340bc4194d7315c6f9f19aabc5f4a5cdc2e22000000000000000000000000ffcc60e7dbf2c9accdb0b8caa699d7b50086c8070000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000091a275da33fe068cd62510b8e3af7818ede891cdff0000000000000000000000000005ba1044cbc00000000000000000000000000000015549b2f3b4007ddefa2f027691116d0a7aa6418246622d70b12a6a27a1a4dd4981e40f406dcef00a654b997f0d1e97b9c9d904e497d6770822215c49b80b54abe913192231475ce47b6ca4a38518440e209941e0592d6bc414891b00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000413a177d93f69420b30a4b870a016171e2b088b8db1ffddab4221c5e326c4bfd3101afb0daad0e623f926ac626248bdeb3b08ef2e9781478f3c78961af4fb4e7931b00000000000000000000000000000000000000000000000000000000000000 ``` To do that , the only way right now would be to slice off...
This should not be necessary and is not something that `graph-node` supports.
Add a migration to graph-cli to use the new POI hash by default. https://github.com/graphprotocol/graph-node/issues/3220