-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Adapt Che-Theia Activity Tracker extension to DevWorkspace mode #20460
Adapt Che-Theia Activity Tracker extension to DevWorkspace mode #20460
Comments
Let me know once an endpoint on Machine Exec side is ready. |
@azatsarynnyy It's already there |
Thanks! We'll look at it next sprint. |
@vzhukovs could you give a brief update on the state of the work - what has been done and what problems still need to be solved? |
@azatsarynnyy sure. The code for implementing http requests has been written and correct endpoint has been obtained. But on minikube with dev workspace mode enabled there is a problem with sending request to machine exec. It seems, that there is something wrong with the certificates or with forming certificate bundle. This is the last thing that left. Investigating how to workaround it. |
Is your enhancement related to a problem? Please describe
Currently, DevWorkspaces are not idled by timeout.
Describe the solution you'd like
We agreed to cover that is currently working for workspaces powered by Che Server workspace engine. As it's relatively cheap to do. So, it's needed to adapt the activity Theia plugin to be run in DevWorkpsace mode, there is should report their activities to Che Machine Exec instead of Che Server. It's POST without body to
/activity/tick
API pathDescribe alternatives you've considered
The alternative is to handle that on Che level but not editor, but it's something we plan to do in #20345
Additional context
No response
The text was updated successfully, but these errors were encountered: