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

Create a project bug - Error messaging saying that my address is being used for another project, but it isn't/shouldn't be #4914

Open
laurenluz opened this issue Dec 30, 2024 · 16 comments
Assignees
Labels
bug Something isn't working

Comments

@laurenluz
Copy link
Member

I was editing the Giveth project.
First, I made edits and then published. Then, I realized there was a mistake, so went to make one more edit in the body again (while it was unlisted).
After editing the body, I wasn't able to "publish" because now it claimed that my address giv.eth was being used for another project - but I didn't change the address, so that's impossible.

I think there is an issue happening somehow where if the project is unlisted, our checks on the address are bugging out.

cc @divine-comedian

image

@github-project-automation github-project-automation bot moved this to New Issues in All-Devs Dec 30, 2024
@laurenluz laurenluz added the bug Something isn't working label Dec 30, 2024
@divine-comedian
Copy link
Contributor

@laurenluz if you made the edits, published, listed it in the admin again then made edits again (causing it to become unlisted) then the error above did not occur?

@kkatusic
Copy link
Collaborator

@laurenluz, cc @divine-comedian, I found one project that is using same address for Arbitrum network: https://giveth.io/project/1-0?tab=donations

@divine-comedian divine-comedian moved this from New Issues to Product Backlog in All-Devs Dec 31, 2024
@laurenluz
Copy link
Member Author

I tried again, and actually, yeah, I have the same issue even if it's listed.
however, I didn't have this issue the FIRST time I pushed the edit. on the 2nd time...

A fix that would help: that project @kkatusic you mentioned is inactive. projects that are inactive should not conflict with active projects if they have the same address.

There are more issues on create a project happening too wrt to this image thing:

For example:

  • when I add an image, for no reason at all, it just shows me it blurry. sometimes this doesn't happen with the same image.
  • the bounds of the image go beyond the bounds of the editing box
Screen.Recording.2025-01-03.at.5.22.54.PM.mov

@kkatusic
Copy link
Collaborator

kkatusic commented Jan 6, 2025

@laurenluz we didn't fix issue, I just wrote what is problem is, same address on some project, let's ask @divine-comedian what behaviour I will use to solve this:

  • remove wallet address from that project and add new one on it?
  • remove that project?
  • write code that will exclude checking address on project that are inactive?

or you can always propose some better solution and I will implement it.

@laurenluz I will check this image issue inside editor, just one notice here, that editor should be updated to newest version but we have some problem with its dependencies.

@kkatusic
Copy link
Collaborator

kkatusic commented Jan 6, 2025

@laurenluz I checked image behaviours inside editor, blurred image is showing you that is process of the uploading same in progress, take some time for the larger images.

The bounds go outside like you wrote, we need to check editor update does same behaviour has been fixed.

@laurenluz
Copy link
Member Author

@kkatusic I think the best solution for the address issue is the 3rd one: write code that will exclude checking address on project that are inactive.

Projects become inactive when the project owner decides to do it. They may one day want to come back to reactivate it. Likely not, but possible.

did you already upgrade the image editor?

@divine-comedian
Copy link
Contributor

divine-comedian commented Jan 6, 2025

@kkatusic I think the best solution for the address issue is the 3rd one: write code that will exclude checking address on project that are inactive.

Projects become inactive when the project owner decides to do it. They may one day want to come back to reactivate it. Likely not, but possible.

did you already upgrade the image editor?

I don't think this is a good idea, since we will run into issues if/when a project chooses to reactivate, this can be done arbitrarily by the user at anytime and we will run into issues later on trying to fix that bug.

Looking at this project conflict specifically I think it is safe to remove the address from https://giveth.io/project/1-0?tab=donations and we can replace it with the same address they have used on all other chains -> 0x882a8CA69f4ae29271816837FD12b144d60f8fA7

@divine-comedian
Copy link
Contributor

I tried again, and actually, yeah, I have the same issue even if it's listed. however, I didn't have this issue the FIRST time I pushed the edit. on the 2nd time...

A fix that would help: that project @kkatusic you mentioned is inactive. projects that are inactive should not conflict with active projects if they have the same address.

There are more issues on create a project happening too wrt to this image thing:

For example:

  • when I add an image, for no reason at all, it just shows me it blurry. sometimes this doesn't happen with the same image.
  • the bounds of the image go beyond the bounds of the editing box

Screen.Recording.2025-01-03.at.5.22.54.PM.mov

I follow up this issue here- > #4925

@laurenluz
Copy link
Member Author

laurenluz commented Jan 6, 2025

I don't think this is a good idea, since we will run into issues if/when a project chooses to reactivate, this can be done arbitrarily by the user at anytime and we will run into issues later on trying to fix that bug.

We should just plan for that within the flow. When they try to reactivate - if someone else used that address for another project - they could get some message like: "oops, that address is being used by another project. change the recipient address in order to reactivate the project". and ofc, we'd need to allow people to edit inactive projects.

If we do anything to address it, there would need to be some user flow designed for it. removing wallet addresses might confuse people, and removing the project when someone sets it as inactive is not really a good option because as you said, someone might even do this by accident.

@divine-comedian
Copy link
Contributor

divine-comedian commented Jan 6, 2025

I don't think this is a good idea, since we will run into issues if/when a project chooses to reactivate, this can be done arbitrarily by the user at anytime and we will run into issues later on trying to fix that bug.

We should just plan for that within the flow. When they try to reactivate - if someone else used that address for another project - they could get some message like: "oops, that address is being used by another project. change the recipient address in order to reactivate the project". and ofc, we'd need to allow people to edit inactive projects.

If we do anything to address it, there would need to be some user flow designed for it. removing wallet addresses might confuse people, and removing the project when someone sets it as inactive is not really a good option because as you said, someone might even do this by accident.

I think this will create more complexities especially in the back-end where we store the project data. The impact-graph is a very fickle beast these days.

We noticed that this validation of checking existing recipient addresses should have been happening more consistently and for some reason it only started working recently - even though the code remained unchanged for 3 years...

The quickest and most direct solution is to edit the project data that is interfering with updating the Giveth project and let's keep a close eye if similar issues are being reported by users. If so we might have to focus on finding a more complex solution.

@laurenluz
Copy link
Member Author

sounds good. so @kkatusic maybe just remove the giv.eth address from that (inactive) project...

But worth noting that also, when I created the issue initially... those addresses were used for the giveth project already (I didn't edit them for a long long time) so there was some error in our system prior to me creating the issue that led to the duplication in the first place.

@divine-comedian
Copy link
Contributor

sounds good. so @kkatusic maybe just remove the giv.eth address from that (inactive) project...

But worth noting that also, when I created the issue initially... those addresses were used for the giveth project already (I didn't edit them for a long long time) so there was some error in our system prior to me creating the issue that led to the duplication in the first place.

Exactly, that's the confusing bit is that some piece of code that hasn't been touched for 3 years is now working, when maybe it wasn't working for... god knows how long

So far I've only heard of this issue from you and Maryjaf cause she has like 3581945197651056914 test projects

@kkatusic
Copy link
Collaborator

kkatusic commented Jan 7, 2025

@laurenluz, cc @divine-comedian, I changed address to that project, setup same main address that project has. Please can you try when you find the time to edit Giveth project and try to save updates.

About how first time you saved changes with no problem, we are investigating that. Some changes can be done via administration. Only connection that we found was that that's address didn't have userId linked.

@maryjaf
Copy link
Collaborator

maryjaf commented Jan 13, 2025

I’m encountering an error on https://giveth.io/project/maryam-test. Could you please apply the same change that you made to the Giveth project to this project as well, so I can test it? @kkatusic

@kkatusic
Copy link
Collaborator

I’m encountering an error on https://giveth.io/project/maryam-test. Could you please apply the same change that you made to the Giveth project to this project as well, so I can test it? @kkatusic

@maryjaf done. Please test it when you find time.

@maryjaf
Copy link
Collaborator

maryjaf commented Jan 13, 2025

Thanks , it has been fixed for me

@maryjaf maryjaf moved this from QA to Done in All-Devs Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants