Skip to content

🐞 [Bug]: Failed to recognize conflicts on creation #13

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

Open
SalmaElsoly opened this issue Feb 26, 2025 · 1 comment
Open

🐞 [Bug]: Failed to recognize conflicts on creation #13

SalmaElsoly opened this issue Feb 26, 2025 · 1 comment
Assignees

Comments

@SalmaElsoly
Copy link
Contributor

SalmaElsoly commented Feb 26, 2025

What happened?

  • On creation of new farm with existing name it respond with {farm_id: 0}

Image

  • On creation of account with existing public key it respond with status code 500

Image

  • On creation of node with duplicate twin id

Image

Cause:

  • gorm doesn't match Postgresql unique constraint error
    solution

which network/s did you face the problem on?

Dev

Twin ID/s

No response

Version

No response

Node ID/s

No response

Farm ID/s

No response

Contract ID/s

No response

Relevant log output

.
@SalmaElsoly SalmaElsoly added the type_bug Something isn't working label Feb 26, 2025
@rawdaGastan rawdaGastan added node-registrar and removed type_bug Something isn't working labels Mar 6, 2025
@Eslam-Nawara Eslam-Nawara self-assigned this Mar 11, 2025
@Eslam-Nawara Eslam-Nawara moved this to In Progress in 3.16.x Mar 11, 2025
@Eslam-Nawara Eslam-Nawara moved this from In Progress to Pending Review in 3.16.x Mar 16, 2025
@Eslam-Nawara Eslam-Nawara moved this from Pending Review to In Verification in 3.16.x Apr 6, 2025
@Eslam-Nawara
Copy link
Collaborator

work completed
we now make sure that farm name is unique on creation and fail if not

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

No branches or pull requests

3 participants