lablup / lablup/backend.ai

cuda.shares human_readable_name displays incorrectly as GPU

Open
#5,144 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
15h 13m
Merged PRs (30d)
368

Description

## Impact

The human_readable_name for cuda.shares is incorrectly displayed as GPU, which can cause confusion for users trying to identify resources accurately.

## Expected behavior

The human_readable_name for cuda.shares should be displayed correctly and distinctively, as fGPU.

## Actual behavior

The human_readable_name for cuda.shares is currently displayed as GPU.

## Steps to reproduce

- Navigate to the relevant section where cuda.shares is displayed.
- Observe the human_readable_name.

## Environment

The issue is present in the dogbowl environment.

## Workarounds

There are currently no known workarounds.

## Other information

No additional information provided.

[View original message posted by Sujin Kim on 7/15/2025, 4:48:59 PM](https://teams.microsoft.com/l/message/19:3c0acc0825024daeb2211f55c4e7f4aa@thread.skype/1752565739281?parentMessageId=1752565739281)

JIRA Issue: BA-1871

Contributor guide

Open the contributing guide

Research direction

Start by locating the definition or display mapping for cuda.shares and inspect how its human_readable_name is currently produced in the dogbowl environment. Confirm that the value is GPU, change the relevant mapping so it displays as fGPU, and verify the resource display no longer uses the incorrect name.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.