-
Notifications
You must be signed in to change notification settings - Fork 864
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
Fix Collectives
location for AHW-next configuration
#7975
base: donal-ah-next-westend
Are you sure you want to change the base?
Conversation
cc: @karolk91 |
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.
Thanks, will change this on AH westend too (it's been like this there since launch I think)
All GitHub workflows were cancelled due to failure one of the required jobs. |
this looks wrong/incorrect - at least unexpected can you also check if it's a bug or intended? if it's intended, make sure to add clear docs/warning to |
ah, nevermind, the problem is with the number of parents - you should change PR description as it is confusing |
Collectives
location for AHW-next configuration
Tested with PET on open-web3-stack/polkadot-ecosystem-tests#210 Works fine |
<Junctions>.into_location()
generatesLocation { parents: 0, interior: <Junctions> }
-parents
defaults to0