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

Consistent ordering of data in the vfolder_mounts field of the compute_session_node query and the mounts field of the compute_session query #3752

Open
ironAiken2 opened this issue Feb 18, 2025 — with Lablup-Issue-Syncer · 0 comments
Assignees

Comments

@ironAiken2
Copy link
Contributor

Summary  

[Provide a brief description of the bug.]  

  • Currently in Backend.AI-WebUI, you can use the folder explorer by clicking the mount folder name in the session detail panel.
  • To use the folder explorer, we need to pass in the vfolder id, and the session detail panel needs to show the vfolder name, so we query the compute_session_node.vfolder_mounts and compute_session.mounts fields, respectively, and navigate through them simultaneously via the Zip method.
  • However, the sort order of the two data does not match, so the vfolder name in the session detail panel and the vfolder name in the folder explorer displayed when clicking on the name do not match.

image-20250218-100842.png{width=1744 height=859}

Steps to Reproduce  

[Outline the steps to consistently reproduce the issue.]  

  1. Create several vfolders of different types.
  2. Create a session by mounting all of the vfolders you created into session.
  3. Click the name in the session list to open the session detail panel and check for bugs.

Expected Behavior  

[Describe the expected result if the bug were resolved.]  

  • The order of the data in compute_session_node.vfolder_mounts and compute_session.mounts must match.

Actual Behavior  

[Describe what actually happens when the bug occurs.]  

Logs/Errors  

[Attach relevant logs, stack traces, or screenshots to help diagnose the issue.]  

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants