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

blockchain: investigate and fix uniqueness constraints on organizations and node addresses #1743

Open
SamuelPull opened this issue Mar 22, 2024 · 2 comments
Assignees

Comments

@SamuelPull
Copy link
Collaborator

          @SamuelPull would you consider other status code? E.g. 409 - conflict, since the input was incorrect due to already existing connection.

Originally posted by @galethil in #1731 (comment)

@SamuelPull SamuelPull self-assigned this Apr 19, 2024
Copy link

stale bot commented Jun 19, 2024

This issue has been automatically marked as stale because it has not had activity for 30 days. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Jun 19, 2024
Copy link

stale bot commented Jun 27, 2024

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Jun 27, 2024
@galethil galethil reopened this Jun 27, 2024
@stale stale bot removed the wontfix This will not be worked on label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants