Unable to see any coin besides Luna
dakom opened this issue · comments
This happens with the latest repo on both Windows and Ubuntu, so I don't think it's a host env problem
Note that also when going to swap, no other coins show
A little more info - hitting http://localhost:3060/terra/oracle/v1beta1/denoms/actives returns an empty list
is your pseudo-feeder running?
@Vritra4 yes, it's running when looking at the current container list
However, if I run docker compose up |grep oracle, it seems that the pricefeeder is failing with a "no aggregate prevote" message error
I wonder if it's that the explicit fee was taken out... 71d4693#diff-54855b3c211c1c73c2545a70b576ed8395ebb84115d405061d2f4255700e8210R136
Will see what happens if I add that back in...
Made a PR which fixes that. But I am still not seeing the full list. Could there be a cacheing issue, or maybe the Docker containers aren't getting it from the local build somehow? Maybe once the PR is merged and the version is bumped it'll magically fix itself... edit: I do see the full list with #65
see #65 (comment) please.
i'll ask to merge #60.
Ok wth... @Vritra4 can you or someone else please explain how this makes any sense?
When I ran my PR it fixes things. Fine. Then I wipe everything:
- all docker containers and images
- the local directory
I then re-clone the repo, and run again (to create a failing case to test against)
And everything is working?!?!?
Latest commit does NOT fix it for me. Fwiw I do see this in the logs, not sure if it's relevant:
TOKEN_NETWORK not defined in environment variable
@dakom still having same issue? hmm it's weird. could you and retry it after pruning docker volumes and images?
the log comes from fcd so i don't think it is related..
Ok, so, consider the shell script below- if I run it, sometimes I can see non-Luna currencies after things start up, sometimes I can't
When I can't, and I wait a bit, it does seem to show, but I can't guarantee that this was the case before (in the past I didn't see anything other than Luna even when waiting and coming back hours later)
If I add the sed command from the Readme (for faster dev time), right before docker-compose up, it seems to not show anything other than Luna even if I wait a bit.
#!/bin/sh
sudo rm -rf ./LocalTerra
docker container kill $(docker container ls -a -q)
docker container rm $(docker container ls -a -q)
docker image rm $(docker image ls -a -q)
docker volume rm $(docker volume ls -q)
git clone --depth 1 https://www.github.com/terra-money/LocalTerra
cd LocalTerra
docker-compose upI can somewhat reliably say that adding the sed in breaks it more often than not having it in... possibly even every time
thanks for your help getting to the bottom of this @Vritra4 ... fwiw I can also say that none of the other devs I am in touch with directly are having this issue, which is extremely strange given that I created a fresh Ubuntu partition to investigate. In case it's relevant, I believe I followed the Docker install/setup instructions here: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04
@dakom i think difference between app.toml(mod by sed) and pseudo-feeder causes the problem. i'll check it. thanks. :)
I've seen this before when the blocktime is sped up, the feeder stops working because the commits happen too often.
which is extremely strange given that I created a fresh Ubuntu partition to investigate.
Did you increase the blocktime in this new instance?
I was also able to replicate this issue when starting a new empty instance of LocalTerra, after a minute or so other balances start populating.
Did you increase the blocktime in this new instance?
I don't think so... where is that changed?
(unless this is affected by the sed command in the README)
Yes! The sed is what speeds up blocktime!
@dakom like @octalmage said, oracle(pseudo-feeder) doesn't work properly when the blocktime is sped up.
so i patched pseudo-feeder :) please see #70. you can test it your own docker image from the PR before the PR merged.
My temporary linux boxed crashed :~(
The original reason I had that was because LocalTerra wasn't working properly for me on M1, I could give that a spin again, but I'm concerned that if that isn't working could be for entirely different reasons
Will update as soon as I can get around to trying LocalTerra somewhere :)
Tried on a windows box, got a "manifest unknown" error
@dakom you need to build your own image because new pseudo-feeder is not published to docker hub yet. :)
steps i tested:
docker build -t pseudofeeder .in pseudo-feeder directory- update image for oracle to pseudofeeder in docker-compose.yml
docker-compose up
Thanks! sorry, forgot to come back and feedback... when I switched machines I wasn't having the problem :/
Very much appreciate the effort in hunting down a "heisenbug" of sorts, cheers!