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

[bug] Go to can trigger exception #71

Closed
nemesifier opened this issue Nov 9, 2020 · 0 comments · Fixed by #74
Closed

[bug] Go to can trigger exception #71

nemesifier opened this issue Nov 9, 2020 · 0 comments · Fixed by #74
Labels
bug Something isn't working

Comments

@nemesifier
Copy link
Member

Found this issue while testing #70.

Subnet using this range: 10.0.0.0/16

If I try to go to 10.250.0.1, the HTTP request generates an exception:

IndexError at /api/v1/subnet/7c173504-6ab6-4051-a036-9ecfe92b122f/hosts/
No exception message supplied

It should return a 400 bad request error which should trigger the "Invalid address" error to be shown in the go to section.

@nemesifier nemesifier added the bug Something isn't working label Nov 9, 2020
@nemesifier nemesifier added this to Backlog in OpenWISP Priorities for next releases via automation Nov 9, 2020
purhan added a commit to purhan/openwisp-ipam that referenced this issue Nov 11, 2020
purhan added a commit to purhan/openwisp-ipam that referenced this issue Nov 11, 2020
purhan added a commit to purhan/openwisp-ipam that referenced this issue Nov 11, 2020
purhan added a commit to purhan/openwisp-ipam that referenced this issue Nov 15, 2020
purhan added a commit to purhan/openwisp-ipam that referenced this issue Nov 20, 2020
OpenWISP Priorities for next releases automation moved this from Backlog to Done Nov 20, 2020
nemesifier pushed a commit that referenced this issue Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging a pull request may close this issue.

1 participant