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 Jul 21, 2024. It is now read-only.
Right now the first term signal is just triggering the termination processes for the service, but not actually shutting down the service. Second one is terminating the process, but it's a second one. It should automatically shutdown when everything is stopped: Agent should stop when it's latest render is downloaded and Manager should stop when all the data is received from the Agents, processed and tasks were saved to continue later.
Environment:
Application version: 0.2.0
Steps to reproduce:
Steps to reproduce the behavior:
Run BlendNet Agent or Manager
Press Ctrl-C
It will say about termination
Wait - it will do nothing
Press Ctrl-C again
The service is terminated
Additional
It's not critical for clouds (just a bit delaying the termination process), but for local provider it could be bad to maintenance.
The text was updated successfully, but these errors were encountered:
Issue description:
Right now the first term signal is just triggering the termination processes for the service, but not actually shutting down the service. Second one is terminating the process, but it's a second one. It should automatically shutdown when everything is stopped: Agent should stop when it's latest render is downloaded and Manager should stop when all the data is received from the Agents, processed and tasks were saved to continue later.
Environment:
Steps to reproduce:
Steps to reproduce the behavior:
Additional
It's not critical for clouds (just a bit delaying the termination process), but for local provider it could be bad to maintenance.
The text was updated successfully, but these errors were encountered: