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.

Sign up for GitHub

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

Jump to bottom

Display of space utilization in rack table is broken #15619

Closed
julianstolp opened this issue Apr 4, 2024 · 3 comments
Closed

Display of space utilization in rack table is broken #15619

julianstolp opened this issue Apr 4, 2024 · 3 comments
Assignees
@jeremystretch
Labels
beta Concerns a bug/feature in a beta release 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

@julianstolp
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.0-beta1

Python Version

3.10

Steps to Reproduce

  1. Open the rack table view /dcim/racks
  2. See SPACE column

Expected Behavior

Open the prefix table view /ipam/prefixes/. The values are displayed so one can read these.
image

Observed Behavior

Space utilization values are not readable
image
@julianstolp julianstolp added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Apr 4, 2024
@jeremystretch jeremystretch changed the title [Beta] Display of spaceutilization in racktable is broken Display of space utilization in rack table is broken Apr 4, 2024
@jeremystretch jeremystretch added the beta Concerns a bug/feature in a beta release label Apr 4, 2024
@DanSheps DanSheps added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 4, 2024
@DanSheps DanSheps removed their assignment Apr 4, 2024
@DanSheps
Copy link
Member

DanSheps commented Apr 4, 2024

This appears to be a dark ui issue, does this issue persist on the light UI as well?

@julianstolp
Copy link
Author

It also persists in the light UI as well. I guess it works for the prefix table because the name utilization is longer than space so the progressbar gets more space.

@jeremystretch
Copy link
Member

It seems the issue here is simply that the column can be too narrow? Setting a minimum width on the bar graph should be sufficient to fix this.

@jeremystretch jeremystretch self-assigned this Apr 5, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Apr 5, 2024
jeremystretch added a commit that referenced this issue Apr 5, 2024
@jeremystretch
Fixes #15619: Enforce a minimum width for progress bars
adb718f
@jeremystretch jeremystretch mentioned this issue Apr 5, 2024
Merged
jeremystretch added a commit that referenced this issue Apr 5, 2024
@jeremystretch
Fixes #15619: Enforce a minimum width for progress bars
ccca058
jeremystretch added a commit that referenced this issue Apr 11, 2024
@jeremystretch
Changelog for #15605, #15616, #15617, #15619, #15637, #15638
379fe7c
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
beta Concerns a bug/feature in a beta release 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DanSheps @jeremystretch @julianstolp