-
-
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
Wrong orgs avatars #5992
Comments
I would love to work on this issue. |
Let me bounty this |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.214 ETH (60.02 USD @ $280.45/ETH) attached to it.
|
Go for it @aranhaagency |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 3 weeks, 6 days from now. 1) kichjang has been approved to start work. There seems to be a couple of reasons why it's not loading correctly, but my hunch is that the image URL for the profile picture is not correct, so I am going to dig right into that. It seems that the URL for the profile image is incorrect. I've used the same URL format to test other user's profile images and haven't been able to reproduce the same problem. I'll investigate further to narrow down where the issue is occurring.
Learn more on the Gitcoin Issue Details page. |
ok seems aranha didn't come so I will accept the next on the list @KiChjang |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 0.214 ETH (55.83 USD @ $260.9/ETH) has been submitted by: @octavioamu please take a look at the submitted work:
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 0.214 ETH (54.64 USD @ $255.32/ETH) attached to this issue has been approved & issued to @KiChjang.
|
Describe the bug
For some reason avatars from some orgs now are failing:
https://gitcoin.co/pegnet
To Reproduce
Expected behavior
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: