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

[CC-PORTAL-FEEDBACK] The rationale should be showing for these votes. #402

Closed
kickloop opened this issue Oct 9, 2024 · 4 comments
Closed
Assignees

Comments

@kickloop
Copy link
Contributor

kickloop commented Oct 9, 2024

Taken at: https://constitution.gov.tools/en/latest-updates
Fields:

  • Noticed an issue?: The rationale should be showing for these votes.

SCREENSHOT
Download original image

Browser: Chrome 129 (Windows 10)
Screen size: 1368x912
Browser size: 1368x785
Open #14 in Usersnap

Powered by Usersnap.

@Thomas-Upfield
Copy link

Thomas-Upfield commented Oct 11, 2024

@Kale98 do you yet have any idea as to why the rationales are not being displayed? I will consider this ticket done when we understand what the problem is, we can have another ticket to fix it if necessary.

@Kale98
Copy link

Kale98 commented Oct 14, 2024

@Thomas-Upfield This issue seams to be caused by the failed connection between Redis and IPFS service. We have reinstalled the services and according to the logs it should be working now. Since we cannot add rationale, do you think you can test that so we can confirm it is working now?
cc @bosko-m

@bosko-m
Copy link

bosko-m commented Oct 15, 2024

As per @Thomas-Upfield comment, if the metadata anchor is stored on chain, why do we need to save it in the database?

@bosko-m
Copy link

bosko-m commented Oct 23, 2024

Impact of rationale not being visible in the application is that people who submitted rationale through the app, most likely didnt get the link to ipfs which means they knew that they were affected or they didnt expect the link at all
All of them actually voted through CLI providing CIP-136 compliant rationale as it can be verified through DBSync records.
Will be addressed in #411 initially then full compliance with CIP-136 should be implemented through #417.

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

No branches or pull requests

4 participants