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 saving device position #11272

Closed
PaulR282 opened this issue Dec 21, 2022 · 2 comments · Fixed by #13502
Closed

Error when saving device position #11272

PaulR282 opened this issue Dec 21, 2022 · 2 comments · Fixed by #13502
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

@PaulR282
Copy link

NetBox version

v3.4.1

Python version

3.10

Steps to Reproduce

  1. Open Netbox in chrome (it works in firefox)
  2. Go to a device
  3. Click edit. The position should say something like UX.0
  4. Click save without changing anything

Expected Behavior

The device should be saved with the position UX.0 or UX

Observed Behavior

The UX.0 gets transformed to UX,0 which can't be saved and an error occurs.

@PaulR282 PaulR282 added the type: bug A confirmed report of unexpected behavior in the application label Dec 21, 2022
@arthanson
Copy link
Collaborator

Just a note, this is related to internationalization (the browser being set to a locale with commas as a separator) - Floats are output with localized decimal separator.

@jeremystretch
Copy link
Member

This has been resolved for now by disabling localization (see #11271).

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2023
@arthanson arthanson reopened this Aug 17, 2023
@arthanson arthanson self-assigned this Aug 17, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Aug 23, 2023
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.

3 participants