starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

GPS search only accepts whole numbers for latitude and longitude #8597

New Issue
Closed
opened 2025-12-29 20:38:39 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:38:39 +01:00
Owner
Copy Link

Originally created by @apm6 on GitHub (Sep 10, 2023).

NetBox version

v3.1.5

Python version

3.10

Steps to Reproduce

Search for a site with a specific latitude or longitude: '/dcim/sites?latitude=43.378470'

Expected Behavior

The API should return a site at that coordinate if there is one.

Observed Behavior

Response is a 400: {'latitude': ['Enter a whole number.']}

I uncovered this issue while trying to search for sites within a gps range. I found that "latitude__lte", "latitude__gte", etc only worked with whole numbers.

Originally created by @apm6 on GitHub (Sep 10, 2023). ### NetBox version v3.1.5 ### Python version 3.10 ### Steps to Reproduce Search for a site with a specific latitude or longitude: '/dcim/sites?latitude=43.378470' ### Expected Behavior The API should return a site at that coordinate if there is one. ### Observed Behavior Response is a 400: {'latitude': ['Enter a whole number.']} I uncovered this issue while trying to search for sites within a gps range. I found that "latitude__lte", "latitude__gte", etc only worked with whole numbers.
adam added the type: bug label 2025-12-29 20:38:39 +01:00
adam closed this issue 2025-12-29 20:38:39 +01:00
adam commented 2025-12-29 20:38:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 11, 2023):

I cannot replicate this on NetBox v3.6.1.

v3.1.5

Your version of NetBox is very old. Please upgrade to the most recent stable release, as it appears the bug no longer exists.

@jeremystretch commented on GitHub (Sep 11, 2023): I cannot replicate this on NetBox v3.6.1. > v3.1.5 Your version of NetBox is _very_ old. Please upgrade to the most recent stable release, as it appears the bug no longer exists.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8597
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?