-
Notifications
You must be signed in to change notification settings - Fork 54
Is this repo still active? And does it work for anyone? #53
Comments
Thanks for reporting, the opensource version was a bit off the radar recently to be honest. Most of the time the cause is a missing version bump from the dependencies of libraries we are actively maintaining (like I updated the |
Great! Thank you very much!! |
So the quick deployment works. But for the public Substrate RPC I still get errors. I can display Finalized block, transactions, module events, active accounts, runtime versions. At 8080 I still get the CORS error: At 8081 I still get the: In the docker logs I get the following error: The complete logs dump: harvester-worker_1 | sqlalchemy.exc.ProgrammingError: (mysql.connector.errors.ProgrammingError) 1146 (42S02): Table 'polkascan.harvester_status' doesn't exist |
I've tried to run the 3 docker options (quick, public and full) for a week now, but unfortunately without any success.
For me, the UI starts, but no data visible.
For:
docker-compose -p kusama -f docker-compose.kusama-quick.yml up --build
At localhost:8080 in the inspector I see on my PC (windows):
<GET https://explorer-31.polkascan.io/api/v1/kusama/balances/transfer net::ERR_CONNECTION_TIMED_OUT>
same timeout error for networkstats/latest and /block
on OSX I get:
Access to XMLHttpRequest at 'http://127.0.0.1:8080/api/v1/networkstats/latest' from origin 'http://localhost:8080' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
if anyone knows how to solve this issue I would be pleased to know^^
At localhost:8081 in the inspector i see:
react_devtools_backend.js: RPC-CORE: getMetadata(at?: BlockHash): Metadata:: createType(Metadata):: Unable to create Enum via index 13, in V0, V1, V2, V3, V4, V5, V6, V7, V8, V9, V10, V11
3. question: Does this mean, that my docker container doesn't run the up-to date python files, because V12 is implemented in the python files of the repo?
For:
docker-compose -p kusama -f docker-compose.kusama-public.yml up --build
I see on localhost:8080 the same CORS error but on my PC
(all containers are up and running)
On the harvester monitor I see a failure for: app.tasks.start_sequencer, app.tasks.accumulate_block_recursive (args: ('0xbc1afbbec4d7d28f267ee2aa5b1f015548d81d59d3e0c32e4286f1b138f4e667', None) )
in the log of docker I see:
harvester-worker_1 | [2021-06-09 12:24:49,073: WARNING/ForkPoolWorker-2] Metadata: CACHE MISS
harvester-worker_1 | [2021-06-09 12:24:49,073: WARNING/ForkPoolWorker-2] 9040
harvester-worker_1 | [2021-06-09 12:24:49,159: WARNING/ForkPoolWorker-2] store version to db
harvester-worker_1 | [2021-06-09 12:24:49,159: WARNING/ForkPoolWorker-2] MetadataV13Decoder
harvester-worker_1 | [2021-06-09 12:24:49,504: INFO/ForkPoolWorker-8] Task app.tasks.start_sequencer[3bd9e224-c707-4e46-be87-132da8b70327] succeeded in 1.6601815999893006s: {'result': 'Chain not at genesis'}
harvester-worker_1 | [2021-06-09 12:24:53,817: WARNING/ForkPoolWorker-2] ! ERROR adding 0x842598b55b65e8aa30eaf89183ef0aca2c1c0438633cdd8b23d1d8fb9adbbf91
harvester-worker_1 | [2021-06-09 12:24:53,818: ERROR/ForkPoolWorker-2] Task app.tasks.accumulate_block_recursive[753031eb-56de-4924-89e8-5883e9d76800] raised unexpected: HarvesterCouldNotAddBlock('0x842598b55b65e8aa30eaf89183ef0aca2c1c0438633cdd8b23d1d8fb9adbbf91')
For:
docker-compose -p kusama -f docker-compose.kusama-full.yml up --build
same error as the one from public.
My ultimate goal is to run the docker-compose.substrate-node-template.yml for my own node.
If I understood correctly, I would only have to specify the template app/type_registry/custom_types.json and the endpoint of my nodes then the MySQL database should be able to store the extrinsics of my nodes and I should have the same behaviour as the polkascan.io view offers, right?
Sidenote1: I saw, that in the docker-compose files Substrate_Metadata_Version=9, shouldn't it be =12?
Sidenote2: the command <git submodule update --init --recursive> didn't update the submodules to the lastest version, so I checked out master in each of them.
Sidenote3: I am aware that this are many questions (sry for that). Should I split them into different issues?
The text was updated successfully, but these errors were encountered: