Closed samuel-p closed 2 years ago
It's likely a corrupt entry in database.
the cause of this I'm not aware of ... but I'll created a pull to least report back instead of panic -> #582
just guessing: PS: you have to stop not kill the agent or else it wont have time to report back new state of running tasks PS: PS: if server is already down before the agent ... it has a similar effect ... we are of it and looking for solutions
Component
server
Describe the bug
With the latest Docker image I get an runtime error after the agent connects to the server:
System Info
Version
Config
Additional context
No response
Validations