-
Notifications
You must be signed in to change notification settings - Fork 67
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
Review Interest interface doesn't stop users from registering an empty string as an interest #4504
Labels
Milestone
Comments
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Nov 28, 2024
mauromsl
added a commit
that referenced
this issue
Feb 12, 2025
mauromsl
added a commit
that referenced
this issue
Feb 12, 2025
mauromsl
added a commit
that referenced
this issue
Feb 12, 2025
mauromsl
added a commit
that referenced
this issue
Feb 12, 2025
mauromsl
added a commit
that referenced
this issue
Feb 12, 2025
mauromsl
added a commit
that referenced
this issue
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
On one of our production installations, we found a server error that was raised from multiple entries existing for the empty string.
The first problem was that an empty string can end up in the list. The second, is that there are no constraints in the database to guard against duplicate Interests from being inserted.
Janeway version
v1.7.2
The text was updated successfully, but these errors were encountered: