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
The way to by-pass the rate limits on the test net is to spin up our own test instance when building. This is relatively easily done using the stellar docker quickstart image:
However, it takes time to catch up with the network so if it were to be used immediately after running the specs we'd have an issue with no data being present. To combat that we need to have a script that looks at the info end point and evaluates if it's caught up. If it's up to date it's exits, if it's not, then it sleeps a second and checks again:
The easiest thing to do is to write this in rust so that it works with the current travis environment without needing to pull in something else. It might make sense to implement this in the CLI itself to pull up the info from a node. This has other benefits as well as it can allow people to introspect their own nodes via command line easily.
Once the script is done, it's just a matter of booting docker and then blocking.
The text was updated successfully, but these errors were encountered:
The way to by-pass the rate limits on the test net is to spin up our own test instance when building. This is relatively easily done using the stellar docker quickstart image:
https://hub.docker.com/r/stellar/quickstart/
We can run this in daemon mode following this travis guide:
https://docs.travis-ci.com/user/docker/
However, it takes time to catch up with the network so if it were to be used immediately after running the specs we'd have an issue with no data being present. To combat that we need to have a script that looks at the info end point and evaluates if it's caught up. If it's up to date it's exits, if it's not, then it sleeps a second and checks again:
The easiest thing to do is to write this in rust so that it works with the current travis environment without needing to pull in something else. It might make sense to implement this in the CLI itself to pull up the info from a node. This has other benefits as well as it can allow people to introspect their own nodes via command line easily.
Once the script is done, it's just a matter of booting docker and then blocking.
The text was updated successfully, but these errors were encountered: