Problem with app using windows
Describe the bug
When I start running from code, which means running {skywire-repo-code-dir}cmd\skywire-visor>go run skywire-visor.go using windows and I have apps in the config file and the apps folder, it does not matter if the config file has the autostart property set to true, the app has to be started manually. Also, there is an error trying to stop the app. I tested this with the Skychat app
Environment information:
- OS: Windows 10
- Platform: x86_64
Steps to Reproduce Steps to reproduce the behavior:
- Compile the Skychat app and put it inside the apps directori on
{skywire-repo-code-dir}cmd\skywire-visor - Create a configuration for being able to run the visor as an hypervisor with Skychat set to autostart.
- Start the visor with
{skywire-repo-code-dir}cmd\skywire-visor>go run skywire-visor.goand open the UI. The app will appear as not started. - Start the app with the UI and wait for the state to be green.
- Stop the app. The procedure will fail with this error:
Not Connected., but the state inside the UI will change to red. - Try to start the app again. The state will be yellow for a moment but will change to an error after a moment.
Actual behavior There are several error, as explained.
Expected behavior All actions should work as expected.
debug logging might be helpful on this
skywire-visor --loglvl debug
typically you'll see logging that says the app was started or not and the error
When stoping, the console only shows this:
After this, the Hypervisor UI shows the app as stopped, as the API returns 0 as the status of the app,, but it in fact continues running, as I can access the Skychat UI via 127.0.0.1:8001
If I try to open it again, There are errors, but it should be because the app is still running, as it shows Error listening network skynet on port 1: port already bound
All this appears to mean that there is a problem with the procedure to stop the app.
Also, when stating the visor, it shows No app discovery associated with app. ←[0;34mappName←[0m="skychat". That may have something to do with the app not starting automatically.