Autostart has issues #56

Closed
opened 2020-03-16 04:44:11 +00:00 by jamie · 5 comments
jamie commented 2020-03-16 04:44:11 +00:00 (Migrated from git.hazaar.io)

Looks like Control tries to autostart even though Warlock is already running. This could be because Control is unable to detect that Warlock is running. THis would also explain why the autostart says it failed even though it actually starts the server because Control is unable to detect that it is running.

Looks like *Control* tries to autostart even though Warlock is already running. This could be because Control is unable to detect that Warlock is running. THis would also explain why the autostart says it failed even though it actually starts the server because *Control* is unable to detect that it is running.
jamie commented 2020-03-16 04:44:11 +00:00 (Migrated from git.hazaar.io)

changed milestone to %1

changed milestone to %1
jamie commented 2020-03-16 04:44:20 +00:00 (Migrated from git.hazaar.io)

created merge request !28 to address this issue

created merge request !28 to address this issue
jamie commented 2020-03-16 04:44:20 +00:00 (Migrated from git.hazaar.io)

mentioned in merge request !28

mentioned in merge request !28
jamie commented 2020-03-16 06:02:21 +00:00 (Migrated from git.hazaar.io)

closed via merge request !28

closed via merge request !28
jamie commented 2020-03-16 06:02:21 +00:00 (Migrated from git.hazaar.io)

mentioned in commit 16c8f0d5f8

mentioned in commit 16c8f0d5f8b73bfc94c4c7444a7d38063572e8c2
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#56
No description provided.