-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Attest the ranked projects inside a category. #9
Comments
@mmahdigh I updated the issue. |
@mmahdigh I provided the link to the |
By tapping on submit vote, I got an error @mmahdigh Payload: |
Can you retest it now? The summation of your shares is 99.97% that's why our backend was declining it. I lowered the sensitivity for now. |
@Meriem-BM Could you take a look and investigate why is the summation 99.97%? My guess is that you're cutting share numbers to 4 decimal places (see the payload) and that's why we're short 0.03%. Let's keep at least 6 decimal places and only for the sake of showing the number in the input, show them rounded to 4 decimal places. Let me know if it's something else or unavoidable. |
Screen.Recording.2024-10-28.at.4.38.09.PM.movScreen.Recording.2024-10-28.at.4.36.19.PM.mov |
Would you please give me your wallet address? |
0xA1179f64638adb613DDAAc32D918EB6BEB824104 @mmahdigh |
Okay, It was a bug in calculating progress and finishing collections automatically. You gamed the system by giving every project a 1-star 😆 I reduced the number of comparisons for the time being so you can get to the end of comparisons faster. I think you can successfully finish the attestation flow now. |
@mmahdigh if you merge the @Meriem-BM PR then we test again |
She hasn't asked for a review yet. @MoeNick |
Thanks @Meriem-BM @mmahdigh |
a new problem happens in attest flow @mmahdigh https://github.com/user-attachments/assets/d6440d54-9293-4639-88a9-dc8691608b5a |
Thanks @Meriem-BM This problem has been fixed
|
Screen.Recording.2024-10-30.at.2.23.59.PM.mov |
@mmahdigh Do you know what should be triggered here? I haven't added anything yet, as well as for the Delegate button next to the budget bar. |
The |
Yes when attested we have |
Can you test these @maryjaf |
this is ready for testing @Meriem-BM or only attest link ? |
I haven't seen finished status for category, after completing ranking and before submitting vot I see below view |
We didn't have that on the Figma designs, @MoeNick, should I add a status for case when comparison is done? |
No we SHOULD NOT have finished status in UI, it's only voted. my comments was for backedn and finished / attested meaning. |
In above picture we should have |
|
@maryjaf you can test this one |
I couldn't complete the submit vote flow because of this |
It hasn't been fixed : @Meriem-BM Screen.Recording.2024-10-31.at.12.07.22.AM.mov |
What's the status of that category @maryjaf? if it's done with comparison, then that's expected before it's attested. @MoeNick told me to redirect to last comparison and show that modal. |
it's done with comparison(but not attested) and base on above comment the status should be voting and vote button should be shown current behavior : Screen.Recording.2024-10-31.at.8.52.04.PM.mov |
Got it, my bad, I should keep the voting status |
@maryjaf can you check this please |
Thanks @Meriem-BM current behavior : |
As a user, after I finish voting a Pairwise ranking and before I have been sent back to the categories page, I want to cast my vote on-chain by an attestation.
Design:
https://www.figma.com/design/tP7Arb2C8aDB05wCVxVVSB/Pairwise-RF6--%3E-Voting-App?node-id=1175-35870&t=vkHFl1L2Am6QdxHX-4
Success Criteria
voted
NOTE: if the user has not voted on a category yet, logging in with an email modal is required.
The text was updated successfully, but these errors were encountered: