You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a deployment has been copied, the IPFS hash does not identify the deployment uniquely any more, and there will be two (or more) deployments with the same hash. graph-node's JSON-RPC reassign_subgraph request fails because a lookup of that IPFS hash returns multiple deployments.
The call handler should be changed so that reassign_subgraph always changes the active copy if there are multiple copies of a deployment.
On the network, this issue causes the indexer-agent to get stuck since it tries to reassign subgraphs
The text was updated successfully, but these errors were encountered:
The reassign_subgraph JSON-RPC call will fail if a deployment exists in
multiple shards. To disambiguate that, change the call so that it only
affects the active deployment.
Fixes#4394
The reassign_subgraph JSON-RPC call will fail if a deployment exists in
multiple shards. To disambiguate that, change the call so that it only
affects the active deployment.
Fixes#4394
The reassign_subgraph JSON-RPC call will fail if a deployment exists in
multiple shards. To disambiguate that, change the call so that it only
affects the active deployment.
Fixes#4394
When a deployment has been copied, the IPFS hash does not identify the deployment uniquely any more, and there will be two (or more) deployments with the same hash.
graph-node
's JSON-RPCreassign_subgraph
request fails because a lookup of that IPFS hash returns multiple deployments.The call handler should be changed so that
reassign_subgraph
always changes the active copy if there are multiple copies of a deployment.On the network, this issue causes the indexer-agent to get stuck since it tries to reassign subgraphs
The text was updated successfully, but these errors were encountered: