Closed suntzu93 closed 1 year ago
@suntzu93 Could you post the associated config file?
Also, as a sanity check, please try running this with execution_mode = "rules"
. Just to make sure that it'll actually run end-to-end.
my config :
id = "0x1b7e0068ca1d7929c8c56408d766e1510e54d98d"
writedir = "data"
max_allocations = 10
whitelist = []
blacklist = []
frozenlist = ["QmdCYUNpfWAE1WnxmV8D3uF6bTG4v1Pz1vFwH1ixASVqnD"]
pinnedlist = []
allocation_lifetime = 5
gas = 100
min_signal = 1000
verbose = true
num_reported_options = 2
execution_mode = "actionqueue"
indexer_url="http://localhost:8000"
network_subgraph_endpoint="https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum"
this is log with execution_mode = "rules"
, nothing happen.
[ Info: Querying data from https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum
[ Info: Writing table to data/indexer.csv
[ Info: Writing table to data/allocation.csv
[ Info: Writing table to data/subgraph.csv
[ Info: Writing table to data/network.csv
[ Info: Optimizing
[ Info: Writing results report
[ Info: Executing best strategy
graph indexer rules stop QmRhYzT8HEZ9LziQhP6JfNfd4co9A7muUYQhPMJsMUojSF
graph indexer rules stop QmThfpPfhwWz1tX8vWtiE7d6tF5KWvJ1nUgFCPRsB359tW
graph indexer rules stop QmVbiz3FCPGTvmuWTyV45JKQAE7JGDmZCkRwQSqTYaR2Er
graph indexer rules stop QmVmmRFcY5szJNvnkz7cZwWLpogyFWfcSXYyQejhJF7mBt
graph indexer rules stop QmW72yLHBi9rtxEYHwci2KDMApigSRVSiKF8GPQ8eboroD
graph indexer rules stop QmYHc14knquHS4aL84JjZxiXg3gGGSqRJHd2ByzjdCrtXy
graph indexer rules stop Qma7bdQ3t7PpN19Qc4h37umg7ffZA3PyKNyNjb5koYNqVb
graph indexer rules stop Qmb9vnaGFvjorr1jnVr55tR43ezxJrev8WHkpR7e9c4it7
Check allocation status being closed before submitting: graph indexer rules set Qmb9vnaGFvjorr1jnVr55tR43ezxJrev8WHkpR7e9c4it7 decisionBasis always allocationAmount 652174.7
Alright perfect. That helps me narrow down what's going on. At this point, we're sure it's action queue related, which I thought was the case from the stacktrace. I'm unsure whether the problem is with the endpoint in your config file "http://localhost:8000"
or if it's some problem on our end. @hopeyen is probably better placed to help you with that since I don't have an instance of the action queue that I can test against. I'll hand this issue to her.
Hi @suntzu93 , I think Ani has the right question here. Is http://localhost:8000
your indexer management server url? Are you able to ping the url from the machine you have optimizer running with and receive results like below?
> curl http://localhost:18000
Ready to roll!%
(I have the typical default (18000), and actions were sent successfully to the indexer on my end.
@hopeyen sorry my bad , 18000
is correct , you guys should be update 8000
to 18000
from this docs https://github.com/graphprotocol/allocation-optimizer/blob/main/docs/src/configuration.md#actionqueue
I changed to 18000
but nothing happen after run tool with execution_mode = "rules"
:
[ Info: Querying data from https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum
[ Info: Writing table to data/indexer.csv
[ Info: Writing table to data/allocation.csv
[ Info: Writing table to data/subgraph.csv
[ Info: Writing table to data/network.csv
[ Info: Optimizing
[ Info: Writing results report
[ Info: Executing best strategy
graph indexer rules stop QmRhYzT8HEZ9LziQhP6JfNfd4co9A7muUYQhPMJsMUojSF
graph indexer rules stop QmThfpPfhwWz1tX8vWtiE7d6tF5KWvJ1nUgFCPRsB359tW
graph indexer rules stop QmVbiz3FCPGTvmuWTyV45JKQAE7JGDmZCkRwQSqTYaR2Er
graph indexer rules stop QmVmmRFcY5szJNvnkz7cZwWLpogyFWfcSXYyQejhJF7mBt
graph indexer rules stop QmW72yLHBi9rtxEYHwci2KDMApigSRVSiKF8GPQ8eboroD
graph indexer rules stop QmYHc14knquHS4aL84JjZxiXg3gGGSqRJHd2ByzjdCrtXy
graph indexer rules stop Qma7bdQ3t7PpN19Qc4h37umg7ffZA3PyKNyNjb5koYNqVb
graph indexer rules stop Qmb9vnaGFvjorr1jnVr55tR43ezxJrev8WHkpR7e9c4it7
Check allocation status being closed before submitting: graph indexer rules set Qmb9vnaGFvjorr1jnVr55tR43ezxJrev8WHkpR7e9c4it7 decisionBasis always allocationAmount 652174.7
execution_mode="actionqueue"
:
[ Info: Querying data from https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum
[ Info: Writing table to data/indexer.csv
[ Info: Writing table to data/allocation.csv
[ Info: Writing table to data/subgraph.csv
[ Info: Writing table to data/network.csv
[ Info: Optimizing
[ Info: Writing results report
[ Info: Executing best strategy
Cool! Will update the docs.
Did your indexer agent receive any POST requests when the tool has executed the strategy? The resulted actions should be pushed to the action queue
Cool! Will update the docs.
Did your indexer agent receive any POST requests when the tool has executed the strategy? The resulted actions should be pushed to the action queue
Thanks, there is an error on my tool side so it doesn't show any action queue, check by cli it has been added to the queue.
I tried latest version
v2.1.1
and got this error :