A user was leaving GajuMine open overnight with an attached GajuDesk window, which gives us a window into what leaving GajuDesk open for a long time does. It turns out what it does is it notices every time we screw things up in the public nodes, and crashes... At least, that is what I would guess, looking at the logs. There's various failed requests, and then eventually the check_balance call specifically starts failing in a way that triggers the supervisor tree. The GajuMine detail is its own issue, issue #10 to be exact, but the underlying crash is probably worth looking at all on its own, one day.
A user was leaving GajuMine open overnight with an attached GajuDesk window, which gives us a window into what leaving GajuDesk open for a long time does. It turns out what it does is it notices every time we screw things up in the public nodes, and crashes... At least, that is what I would guess, looking at the logs. There's various failed requests, and then eventually the check_balance call specifically starts failing in a way that triggers the supervisor tree. The GajuMine detail is its own issue, issue #10 to be exact, but the underlying crash is probably worth looking at all on its own, one day.
This seems related to the problem that previous versions of GajuMine were opening GajuDesk within the same runtime context, and a problem with one became a problem with the other. There were other issues with that approach as well, but this was a lingering one.
This seems related to the problem that previous versions of GajuMine were opening GajuDesk within the same runtime context, and a problem with one became a problem with the other. There were other issues with that approach as well, but this was a lingering one.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A user was leaving GajuMine open overnight with an attached GajuDesk window, which gives us a window into what leaving GajuDesk open for a long time does. It turns out what it does is it notices every time we screw things up in the public nodes, and crashes... At least, that is what I would guess, looking at the logs. There's various failed requests, and then eventually the check_balance call specifically starts failing in a way that triggers the supervisor tree. The GajuMine detail is its own issue, issue #10 to be exact, but the underlying crash is probably worth looking at all on its own, one day.
This seems related to the problem that previous versions of GajuMine were opening GajuDesk within the same runtime context, and a problem with one became a problem with the other. There were other issues with that approach as well, but this was a lingering one.