|
|
I can't reproduce this problem, but "checkonly" is not harmful, so I'll unlock double-executing lock. |
|
|
Hmm... I've looked a little more into it, and realized that the ghost that is having the 'executing' error every time is the only one of my ghosts that also performs a checkonly update for the shell and balloon after checking for ghost updates. That probably is a part of it as well. (This is the ghost in question: https://zichqec.github.io/s-the-skeleton/flux ) I tested with some of my other ghosts, and they seem to give the 'executing' error the first time I try a checkonly update after booting them, and then it works normally after that. It's very strange that they give an executing error before they've done any other checks at all. |
|
|
I've discovered something else, I'm not sure if it's of importance here or not. When my checkonly updates fail, OnUpdateFailure fires instead of OnUpdateCheckFailure. This explains why my ghosts are displaying error messages unexpectedly... image.png (15,093 bytes) |
|
|
2.5.34 |
- Anonymous
