Closed deepsp94 closed 2 years ago
Context regarding the work above (empty commits):
Heroku re-deploys an app only if there is an additional commit. So if a new buildpack is added, it can only be used if the app is re-deployed, which will only happen if there is a new commit. Hence the empty commits.
I needed to install gsl to the heroku app in order to run pystable. There are some gsl buildpacks by the community that are available in the Elements marketplace and elsewhere on the internet. These aren't actively maintained and are either buggy or install really old versions of gsl which aren't useful for running pystable.
The apt buildpack (https://github.com/heroku/heroku-buildpack-apt) coupled with the last commit on this branch (72f0b06
) seems to have done the trick, ie, got pystable running on heroku.
@mikeyrf I have already deployed this branch to my project pipeline on Heroku and can confirm that the scripts run on Heroku. Adding descriptions for important files/changes below so you can prioritise these files as you review the code.
brownie networks add
quotes.json
but named with the prefix "sushi_" so it's understood that these quotes are different from the uni v3 ones. I've retained the original quotes.json
file too so that older deployments don't stop running.ovl_metrics_univ3
. Otherwise, if metrics have never been recorded before then just start from 30 days back.find_start()
and nowinflux_metrics_univ3.py
to calculate 1h TWAP.
What's done:
influx_univ3.py
: Ingesting metrics and catching most exceptionsinflux_metrics_univ3.py
: Calculating metrics using above dataWhat's left:
influx_univ3.py
a bit more resilient. Still facing some time out issues