gituser
commented
3 years ago After bumping polkadot-api to 3.9.3, the crawler seems to be working (not sure), used this commit - https://github.com/Colm3na/polkastats-backend-v3/commit/d6df56b72a971676188897a22f0151c92148b1ac
But I still do not see where should point /api/v3 endpoint, I've tried putting it into 8082 port (hasura/graphql) but it responds with 404 error..
Particularly these endpoints in the polkastats config, what do I specify If I'm using docker (my local ones):
nodeWs: "wss://westend.polkastats.io/rpc",
backendWs: "wss://westend.polkastats.io/api/v3",
backendHttp: "http://westend.polkastats.io/api/v3",EDIT: it seems I've figured it out:
wss://westend.polkastats.io/api/v3 -> points to /v1/graphql which is on port 8082, so in nginx (if you're using one) you need to either rewrite /api/v3 to /v1/graphql or specify graphql endpoint, e.g.:
location /api/v3 {
rewrite /api/v3 /v1/graphql break;
proxy_pass http://127.0.0.1:8082;
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
proxy_set_header X-Forwarded-Proto https;
proxy_redirect off;
proxy_buffering off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}Thought transfers seems to be empty for now on my instance:
Also it seems https://westend.polkastats.io is stuck too on 12th Jan for some reason.
Another issue: on local deployment when visiting any address, e.g. http://localhost:3000/account/5ENpP27BrVdJTdUfY6djmcw3d3xEJ6NzSUU52CCPmGpMrdEY loading data takes forever and nothing is displayed, in console I can see this:
commons.68c530e.js:2 TypeError: address.substring is not a function
at f.shortAddress (index.049fb00.js:1)
at fn (index.049fb00.js:1)
at r (commons.68c530e.js:2)
at In (app.5745132.js:2)
at f.normalizeSlot (app.5745132.js:2)
at f.renderTbodyRowCell (app.5745132.js:2)
at app.5745132.js:2
at Array.map (<anonymous>)
at f.renderTbodyRow (app.5745132.js:2)
at app.5745132.js:2
te @ commons.68c530e.js:2
commons.68c530e.js:2 Error: Invalid character
at n (7a82ef42.6730359.js:2)
at c (7a82ef42.6730359.js:2)
at h._parseBase (7a82ef42.6730359.js:2)
at h._init (7a82ef42.6730359.js:2)
at new h (7a82ef42.6730359.js:2)
at formatAmount (index.049fb00.js:1)
at f.<anonymous> (_id.3e11fbb.js:1)
at f.t._render (commons.68c530e.js:2)
at f.r (commons.68c530e.js:2)
at _n.get (commons.68c530e.js:2)it seems same issue here as well - https://polkastats.io/account/15j4dg5GzsL1bw2U2AWgeyAk6QTxq43V7ZPbXdAmbVLjvDCK
Can you clarify please @mariopino?
Thanks.
Describe the bug
I've tried following the docker-compose process on the latest
developbranch:and getting this on the crawler container:
I've tried both polkadot v0.8.27 and polkadot v0.8.28-1 (latest) - same result.
Also another question is: crawler should be crawling blocks into the postgres and who is serving
/api/endpoint? Is it graphql-container?Thanks.
@mariopino
Expected behavior
Screenshots
Additional context