aws / aws/amazon-sagemaker-feedback

Custom image versions and lifecycle configurations are displayed twice

Open
#152 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Product Version

- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio

### Issue Description

Some problems in the Studio UI:

1. The list of Lifecycle configurations is shown twice:

![Screenshot 2024-12-03 at 16 39 10](https://github.com/user-attachments/assets/d633c144-48d2-4158-95b6-6710e291b87c)

2. The list of image versions are duplicated, even though there is only one image attached:

![Screenshot 2024-12-03 at 16 39 41](https://github.com/user-attachments/assets/366bf52f-d1c7-44ab-8005-378586f74c84)

3. When I click on "run space", the version information is lost from the image:
![Screenshot 2024-12-03 at 16 48 37](https://github.com/user-attachments/assets/1bdd31ed-1317-4a1d-81b4-70948556992f)

(full image names redacted)

I am registering the lifecycle scripts and image versions both in the `JupyterLabAppSettings ` both on the domain level (`DefaultUserSettings`) and the user profile level (`UserSettings`), could this be causing the duplication? I would expect that the UI would filter out the duplicates, since those are essentially the same images and lifecycle scripts.

### Expected Behavior

I expect to see each unique resource only once there.

### Observed Behavior

_No response_

### Product Category

JupyterLab

### Feedback Category

User Interface

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in Amazon SageMaker Studio's JupyterLab UI with the same image version and lifecycle configuration registered at both the domain and user-profile levels. Verify whether duplicate resources appear and whether clicking "run space" drops version information. Done means each unique resource appears once and image version information is retained.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.