David Lutterkort
David Lutterkort
The implementation of declared calls (#5264) does not charge gas when the call is made before running the handler. It will charge gas when the handler actually executes `ethereum.call`, but...
The implementation of declared calls (#5264) only allows declaring them for events. It should also be possible to declare them for call handlers. It might also be desirable to declare...
The implementation of declared calls (#5264) doesn't support overloaded functions. It should.
### Bug report With recent `graph-node` master, this command fails with a complaint about `parentHash`: ``` # graphman chain info mainnet Error: missing field `parentHash` ``` ### Relevant log output...
We need to do something about the `entity_count` for grafts. Right now, when all data has been copied, `graph-node` will fire off a big query that counts the entities in...
### Bug report After all the data for a graft has been copied, we [revert the destination to the graft block](https://github.com/graphprotocol/graph-node/blob/master/store/postgres/src/deployment_store.rs#L1538-L1545) For large subgraphs, that will be very slow. Instead...
### Bug report The code currently copies private data sources [row by row](https://github.com/graphprotocol/graph-node/blob/master/store/postgres/src/dynds/private.rs#L255-L302). Since we are seeing subgraphs with hundreds of thousands of private data sources, mostly file data sources,...
Currently, it is only possible to cancel a copy by unassigning the destination subgraph. It would be better to have an explicit command to cancel such a copy.
### Bug report The following sequence of steps will lead to a grafted (or copied) subgraph with missing dynamic data sources: 1. Start a graft 2. Interrupt it and rewind...
The second commit actually fixes [this bug](https://github.com/graphprotocol/graph-node/issues/5465)