-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
round 8 bug / improve list #7947
Comments
just tested, feels pretty rough. here are my QA notes (all in latest chrome + metamask): showstoppers
major
attention to detail stuff
could not test
|
I added better validation for this but extract the username of any format seems overkill to me. I was looking on some of the possible patterns https://regex101.com/r/s6JoZ5/3 |
testing latest build
|
@chibie could you take a look at the twitter handle ! @owocki looks like there edit grants had to be fixed up a bit cause it was setting ETH payout address to undefined on edit. |
Also I'm still getting the error: zcash_payout_address must be a transparent address when i try to edit any grant, the fix isn't merged yet? |
@zoek1 could you make sure your grant has
and you have the latest changes |
i just dont want the grant creation form to fail validation bc of the lack of an more testing notes:
|
I just pushed a commit adding the sidecart back |
Twitter verification on the Trust Bonus tab is broken in the grants branch, as far as I can tell. Seems like the regression came from this PR, which I commented on with a bit more context: #7962 @zoek1, can you expand on why you were modifying the twitter verification endpoint? That endpoint is used for the Trust Bonus. Was it your intention to change the behavior of the Trust Bonus? |
Attempting to test SMS verification from the Trust Bonus tab gives the following error from the backend:
Has our API key or auth token changed? (Reminder not to post these here) |
Need a bit more direction on how to regression test Google Verification: #7631 (comment) Should still be working but would like to test locally |
edit: fixed via #7977 |
edit: fixed via #7976 allows starting @ symbol or not in frontend while it is stripped in backend per @owocki 's comment above |
While checking out with multiple ETH grants in my cart via zksync, I received an error alert in the UI while I was redirected to the zksync checkout. Zksync checkout worked perfectly as expected, and when finished I was returned to the grants page and received the success modal, but during this time if I return to the cart page the alert is shown which reads "Insufficient balance to complete checkout". I don't know if this refers to the zksync balance being insufficient as I a) did have enough funds in my wallet to complete checkout and b) did not have any L2 funds at this time, but either way if that is "expected behavior" its definitely confusing/scary for users and the copy and alert style need to be changed. |
^ @mds1 |
Hey @danlipert. The insufficient balance modal should only show if you have insufficient funds in both L1 and L2. Can you clarify the steps to reproduce? I'm not sure I follow.
This is the main part I'm confused on. The success modal redirects you off the cart page, so did you then go back the cart, and the cart was not cleared? Or did you add new grants to your cart after? Or something else? Also, what was in your cart at the time of that second checkout? It looks like you may have had an empty "amount" field based on the console error messages showing |
@mds1 I had sufficient funds in L1 but not L2. Not sure exactly how to reproduce. What happened was the zksync flow opened in a new tab, and i went back to the cart tab just to check and the error was there while I was going through the zksync flow. Once I finished the zksync flow I was redirected back to the success modal screen. I took the screenshot while I was going through the zksync flow. I'm pretty sure all the amount fields had something in them as I got the appropriate number of txns in the zksync checkout explorer link list, but they were all very small amounts. |
@danlipert Ahhh I see, got it, thanks for the additional info! I'll look into this today |
Browser: Brave Mac 1.17.73 Major
Minor
|
Thanks @willsputra ! I also just got the SAI / DAI issue but only for one of the grants (gitcoin dev fund optional contribution) so probably has something to do with when the grant was created back when you could specify a specific type of token you accepted. I also received 4 emails for the 4 rolled up zksync contributions :/ But was able to successfully check out. @willsputra the error you got I believe has to do with the calculation of the zksync fee being larger than what you would have saved by using it or something like that.
aditya: reverting the 1 mail -> multi contribution PR would fix this |
|
|
i just got 8 emails from making 8 contributions in 1 cart. is the bulk checkout email going to make it in? aditya: Doubtful ! Given that subscription creation happens in celery. I'm not sure how we'd be able to wait for all celery tasks to be processed and only then send an email ! scope lift is working on it -> but I'm not sure how we'd actually do this |
Replace with |
|
|
|
|
|
Grant in question: https://gitcoin.co/grants/1602/gallerist-by-collectorshub |
cc: @jdorfman |
shows is CLR Eligible in the backend, but when checking out it doesn’t show. |
@vs77bb @ceresstation If you are a team member of a grant, and add that grant to your cart, it will say "Not eligible for CLR" because you don't get matched for donating to a grant you are part of. Both of those grants seem to be working properly We can change that message to me more clear in this case. Let me know if you have any suggestions! |
|
this API is super slow + causes the grants index page to be slow. EDIT: added some indexes in 07a6e67 and its now down to 2s. not super fast but at least not showstopp'y slow anymore
|
|
|
|
https://bits.owocki.com/yAuZvErY round 7 image still showing u8p |
video: https://bits.owocki.com/E0u4b5B1 edit: fixed by 495d0d5 |
Thanks @teohhanhui, I'll relay this to the zkSync team now. What browser and wallet were you using? |
Firefox 84.0b7 (Manjaro Linux) |
|
MAJOR
/
URL to endpoint should not return 404 FIX: 5e56dffMINOR
Add to collection
in card only if user is logged in and has a collection of their own imageThe text was updated successfully, but these errors were encountered: