Closed OverlordQ closed 4 years ago
@OverlordQ Was this with an automatically created directive or a manually placed one? Did you delete the directive?
Also is this on master or dev branch?
Automatic.
No.
Dev.
I threw a try/catch around log.alert(`Removing expired directive ${this.print}!`);
in the Directive constructor and it seems to have moved on.
Of note, this was on the PTR, and might be related to the CPU sub's weekly reset, so things might have gone wonky when the max CPU was chopped to 20CPU.
So whatever cleanup was being done may have only half executed.
This is probably and edge case, but it may or may not crop up again if somebody bangs up against the CPU limit.
Issue summary
Throwing exception when trying to clean up PowerMining Directives
Steps to reproduce:
Error message:
Suggested fix (optional):
Other information:
Commit: c1cccf3