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
Right now, the function waitForAqua which is used whenever we want to check the status of a DDO (for instance on the CLI getDDO command). It does not have a configurable interval to do the checks..
It keeps retrying itself every 1.5 seconds, for a MAX of up to 100 retries... (all hardcoded)
This is kind of pointless if the DDO is taking some time to get indexed..
We should at least double the default interval (so, retry every 3 seconds) and make it a configurable argument for the function. Additionally, the MAX retries could also be configurable
This is also helpful to lower the number of inconsequent requests possible made against the node (which also can post rate/connection limits)
The text was updated successfully, but these errors were encountered:
Right now, the function
waitForAqua
which is used whenever we want to check the status of a DDO (for instance on the CLIgetDDO
command). It does not have a configurable interval to do the checks..It keeps retrying itself every 1.5 seconds, for a MAX of up to 100 retries... (all hardcoded)
This is kind of pointless if the DDO is taking some time to get indexed..
We should at least double the default interval (so, retry every 3 seconds) and make it a configurable argument for the function. Additionally, the MAX retries could also be configurable
This is also helpful to lower the number of inconsequent requests possible made against the node (which also can post rate/connection limits)
The text was updated successfully, but these errors were encountered: