You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
Users of the Cate App backend service should be informed about upcoming auto-shutdown due to inactivity, given that auto-shutdown has been enabled for the service (e.g. cate-webapi-start --auto-stop-after 3600 ...).
Actual behavior
The service stops without notification just leaving a log message.
Steps to reproduce the problem
Run cate-webapi-start --auto-stop-after 100 ... on localhost.
Start Cate App for local service.
In Cate App do nothing else, just wait for "Connection closed" message.
Implementation
Use WebSocket to send JSON RPC message to clients containing time left until auto-close service and time of service inactivity.
Specifications
Cate 3.1.1, Cate App 3.1.0
The text was updated successfully, but these errors were encountered:
This is the backend counterpart for CCI-Tools/cate-app#164.
Expected behavior
Users of the Cate App backend service should be informed about upcoming auto-shutdown due to inactivity, given that auto-shutdown has been enabled for the service (e.g.
cate-webapi-start --auto-stop-after 3600 ...
).Actual behavior
The service stops without notification just leaving a log message.
Steps to reproduce the problem
cate-webapi-start --auto-stop-after 100 ...
on localhost.Implementation
Use WebSocket to send JSON RPC message to clients containing time left until auto-close service and time of service inactivity.
Specifications
Cate 3.1.1, Cate App 3.1.0
The text was updated successfully, but these errors were encountered: