Skip to content

Add workspace session time to gp info #16146

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

Closed
loujaybee opened this issue Feb 1, 2023 · 2 comments
Closed

Add workspace session time to gp info #16146

loujaybee opened this issue Feb 1, 2023 · 2 comments
Labels
component: gp cli feature: timeout meta: stale This issue/PR is stale and will be closed soon

Comments

@loujaybee
Copy link
Member

Currently a workspace cannot run for more than 36 hours continuously. However, there is no way for a user to know officially how long the workspace has been running, and to gauge how much uptime they have left on the running workspace. You can use the uptime command to show the session time, however I'm not sure how accurate this is. It would be good to add both:

  • Current uptime
  • Remaining uptime (36 hours - current uptime)

Into the gp info command, so that users are at least aware of, and can track this limitation.

See related documentation:

And issue:

@akosyakov
Copy link
Member

akosyakov commented Feb 2, 2023

I'm not sure info is a good place. It is rather static info. Maybe top is better? It reflects dynamic characteristics.

@stale
Copy link

stale bot commented May 9, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label May 9, 2023
@stale stale bot closed this as completed Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: gp cli feature: timeout meta: stale This issue/PR is stale and will be closed soon
Projects
None yet
Development

No branches or pull requests

2 participants