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

codegen: is_codegen_valid_for doesn't work as expected for "trimmed metadata" #1286

Closed
niklasad1 opened this issue Nov 23, 2023 · 1 comment · Fixed by #1306
Closed

codegen: is_codegen_valid_for doesn't work as expected for "trimmed metadata" #1286

niklasad1 opened this issue Nov 23, 2023 · 1 comment · Fixed by #1306
Assignees
Labels
bug Something isn't working

Comments

@niklasad1
Copy link
Member

niklasad1 commented Nov 23, 2023

  1. Generate metadata/codegen
$ subxt metadata --url wss://rpc.polkadot.io --pallets "ElectionProviderMultiPhase,System" -f bytes > metadata.scale
  1. Connect to the same node and compare the metadata (this calls "is_codegen_valid_for" internally)
$ ./target/debug/staking-miner --uri wss://rpc.polkadot.io info
Remote_node:
{
  "spec_name": "polkadot",
  "impl_name": "parity-polkadot",
  "spec_version": 9431,
  "impl_version": 0,
  "authoring_version": 0,
  "transaction_version": 24,
  "state_version": 0
}
Compatible: NO

If one just generates "untrimmed metadata" it works as expected.

@jsdw
Copy link
Collaborator

jsdw commented Nov 23, 2023

Oh interesting, it def should work for trimmed metadata, so I geuss there's a bug somewhere!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants