Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not decorating unknown runtime apis #1216

Closed
5 tasks done
AtelyPham opened this issue Jul 27, 2022 · 2 comments · Fixed by #1234
Closed
5 tasks done

Not decorating unknown runtime apis #1216

AtelyPham opened this issue Jul 27, 2022 · 2 comments · Fixed by #1234

Comments

@AtelyPham
Copy link

AtelyPham commented Jul 27, 2022

Prerequisites

  • Are you running the latest version(s)?
  • Did you check the debugging guide?
  • Did you check the FAQs and Discussions?
  • Are you reporting to the correct repository?
  • Did you search for an existing issue or pull request?

Description

Currently, I run the SubQuery project locally using subql-node and connect my index node on a custom Substrate chain (my index node also running locally). I have Postgres v14 installed already. But when I ran subql-node -f ., I got the following output:

Output:
@polkadot/util has multiple versions, ensure that there is only one installed.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
        cjs 10.1.1      node_modules/@subql/node/node_modules/@polkadot/util/cjs
        cjs 9.7.2       node_modules/@subql/node/node_modules/@subql/utils/node_modules/@polkadot/util/cjs
2022-07-28 01:57:31        API/INIT: Not decorating unknown runtime apis: 0x9f5f822b6fd456f6/1, 0x51fffea56fd0c5d4/1, 0x2358a96901b1aa87/1
2022-07-27T18:57:32.058Z <Project> INFO force cleaned schema and tables
2022-07-27T18:57:32.062Z <store> INFO Historical state is disabled
2022-07-27T18:57:32.158Z <dictionary> WARN failed to fetch specVersion result Error: Only absolute URLs are supported
2022-07-27T18:57:32.159Z <subql-node> INFO Node started on port: 3000
2022-07-28 01:57:33        API/INIT: Not decorating unknown runtime apis: 0x9f5f822b6fd456f6/1, 0x51fffea56fd0c5d4/1, 0x2358a96901b1aa87/1
2022-07-28 01:57:33        API/INIT: Not decorating unknown runtime apis: 0x9f5f822b6fd456f6/1, 0x51fffea56fd0c5d4/1, 0x2358a96901b1aa87/1
2022-07-28 01:57:33        API/INIT: Not decorating unknown runtime apis: 0x9f5f822b6fd456f6/1, 0x51fffea56fd0c5d4/1, 0x2358a96901b1aa87/1
2022-07-28 01:57:33        API/INIT: Not decorating unknown runtime apis: 0x9f5f822b6fd456f6/1, 0x51fffea56fd0c5d4/1, 0x2358a96901b1aa87/1
2022-07-28 01:57:33        API/INIT: Not decorating unknown runtime apis: 0x9f5f822b6fd456f6/1, 0x51fffea56fd0c5d4/1, 0x2358a96901b1aa87/1

Also checked my database and it's empty.

Details

These details can help to reproduce the environment the issue is occurring

Local Environment: @subql/cli/1.3.1 darwin-arm64 node-v18.6.0
Query Version: I'm not using subql-query.
Indexer Version: 1.5.1
Network Details:

  • Custom Polkadot Substrate.
  • Endpoint: ws://127.0.0.1:9944 (I can connect to this endpoint using polkadot UI app).

Any other information

Screenshots CleanShot 2022-07-28 at 01 57 36@2x CleanShot 2022-07-28 at 00 03 56@2x
@jiqiang90
Copy link
Contributor

Checked the this seems due to polkadot update in v8.11.1 (https://github.com/polkadot-js/api/releases/tag/v8.11.1).

Now it has type generation for runtime call definitions (internal & external), https://github.com/polkadot-js/api/blob/e4a19dcefda8944a569ff15e52b8f610ee25803a/packages/api/src/base/Decorate.ts#L497

With user provide runtimes (https://github.com/polkadot-js/api/blob/master/packages/api/src/types/index.ts#L68), when we use api.at() method to get current block and decorate our api call this will throw warning each time.

Will send a request to Polkadot for assistant.

@AtelyPham
Copy link
Author

AtelyPham commented Aug 1, 2022

I will wait for update from the team, thanks for the reply 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants