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

error when filtering choice sets when editing/creating a custom field #14239

Closed
ITJamie opened this issue Nov 9, 2023 · 0 comments · Fixed by #14385
Closed

error when filtering choice sets when editing/creating a custom field #14239

ITJamie opened this issue Nov 9, 2023 · 0 comments · Fixed by #14385
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@ITJamie
Copy link
Contributor

ITJamie commented Nov 9, 2023

NetBox version

v.3.6.4

Python version

3.11

Steps to Reproduce

  • create a custom field choice set
  • start creating a custom field. attempt to search in the "choice set" field.

UI error should pop up (or see a failure in browser debug window
error can easily be triggered by going to /api/extras/custom-field-choice-sets/?brief=true&q=abc on a netbox instance

Expected Behavior

choice set should filter

Observed Behavior

error is triggered in browser

<class 'django.db.utils.DataError'>

malformed array literal: "abc"
LINE 1: ... "extras_customfieldchoiceset"."extra_choices" @> 'abc'::var...
                                                             ^
DETAIL:  Array value must start with "{" or dimension information.

Python version: 3.11.4
NetBox version: 3.6.4
Plugins: 
  netbox_gateways: 0.4.3
Screenshot 2023-11-09 at 21 41 43
@ITJamie ITJamie added the type: bug A confirmed report of unexpected behavior in the application label Nov 9, 2023
@jeremystretch jeremystretch self-assigned this Nov 29, 2023
@jeremystretch jeremystretch added severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation labels Nov 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants