-
Notifications
You must be signed in to change notification settings - Fork 28
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
test: make tests work with new kilt node cli #796
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two minor comments.
Do we not have knowledge of how the metadata shape when starting the node? Otherwise, could we utilize the version in the metadata to determine which arguments are required or not?
We don't, as we get the metadata from the node. You probably know more about the node CLI than me, and if we can use it to export the metadata, but using the CLI to avoid breaking changes in the CLI is probably a little circular? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I was thinking that the metadata comes from the started container node but was not sure. LGTM
* test: make tests work with new kilt node cli * test: re-use integration test utils in bundle tests * test: bump runtime version in integration test switch condition
* refactor!: nest ctype in ICTypeDetails (#766) * refactor: change ctype parameter name to cType where possible * feat: re-export imported types from @kiltprotocol/types (#762) * feat: deprecate CType meta schema draft-01 (#778) * fix: default to log level warn in non-production environments * test: skip expensive delegation node tests * test: esm variant of integration tests (#779) * test: make tests work with new kilt node cli (#796) * chore: update metadata to 1.11.0 * chore(deps): update cbor-web to v9 * chore(deps-dev): bump webpack from 5.70.0 to 5.76.0 (#771) * chore(deps-dev): bump semver-regex from 3.1.3 to 3.1.4 (#775) * chore(deps-dev): bump typedoc to resolve dependency conflict * ci: make latest-develop tests optional and latest mandatory Co-authored-by: Gerawork Aynekulu <ggera@users.noreply.github.com> Co-authored-by: Raphael Flechtner <raphael@kilt.io>
fixes KILTProtocol/ticket#2835
A different startup strategy is required for kilt nodes based on polkadot v0.9.43 because the CLI has changed and arguments have been renamed.
This introduces a fallback strategy if the container can't be started, and will try again using a set of arguments which should work for the new CLI.
How to test:
Latest currently uses the old CLI, while latest-develop uses the new CLI. If both integration test runs succeed, this works.
Checklist: