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 on applying filter in circuits #3292

Closed
quentinsch opened this issue Jun 24, 2019 · 2 comments
Closed

Error on applying filter in circuits #3292

quentinsch opened this issue Jun 24, 2019 · 2 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@quentinsch
Copy link

quentinsch commented Jun 24, 2019

Environment

  • Python version: 3.5.3
  • NetBox version: 2.6.0

If you apply or clear any filter in the circuits section I receive an error message:
<class 'ValueError'>
invalid literal for int() with base 10: ''

Screenshot 2019-06-24 at 15 25 24

Other filters in other sections work just fine.

Steps to Reproduce

  1. Go to Circuits
  2. Apply any filter on the right side
  3. An error is shown

Expected Behavior

I expected to apply the filter that I've chosen.

Observed Behavior

An error message was shown and an email was sent by NetBox.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Jun 24, 2019
@jeremystretch
Copy link
Member

This issue seems to occur whenever an integer filter field is passed with no value (in this case, commit_rate). As a workaround, you can omit &commit_rate= from the query parameters in the URL and the request should succeed normally.

I'm still trying to track down what changed to cause this.

@jeremystretch
Copy link
Member

Found it. This is a bug related to #3038.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants