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

NEO: Improve auto refetch handling for session list #3174

Open
yomybaby opened this issue Feb 17, 2025 — with Lablup-Issue-Syncer · 0 comments · Fixed by #3169
Open

NEO: Improve auto refetch handling for session list #3174

yomybaby opened this issue Feb 17, 2025 — with Lablup-Issue-Syncer · 0 comments · Fixed by #3169
Assignees

Comments

@yomybaby
Copy link
Member

yomybaby commented Feb 17, 2025

The objective of this initiative is to enhance the auto refetch functionality for the session list in the NEO application. This improvement aims to ensure that users receive the most up-to-date session information without manual intervention, thereby increasing efficiency and user satisfaction. By refining the auto refetch mechanism, we can minimize delays and ensure a smoother user experience when accessing session data.

@yomybaby yomybaby self-assigned this Feb 17, 2025
graphite-app bot pushed a commit that referenced this issue Feb 17, 2025
resolves #3174 (FR-567)

Adds auto-refresh functionality to the compute session list page with a dedicated refresh button that shows loading state and supports automatic updates every 15 seconds. The table now displays a loading state with reduced opacity during updates and shows the total number of items.

Key changes:
- New `BAIFetchKeyButton` component for manual/automatic data refresh
- Enhanced table loading states with smooth opacity transitions
- Added "Last Updated" translations across all languages
- Improved badge visibility for running sessions
- Fixed state updates in `useDeferredQueryParams` hook
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

Successfully merging a pull request may close this issue.

1 participant