skywire icon indicating copy to clipboard operation
skywire copied to clipboard

Problem with app using windows

Open Senyoret1 opened this issue 2 years ago • 2 comments

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:

  1. Compile the Skychat app and put it inside the apps directori on {skywire-repo-code-dir}cmd\skywire-visor
  2. Create a configuration for being able to run the visor as an hypervisor with Skychat set to autostart.
  3. Start the visor with {skywire-repo-code-dir}cmd\skywire-visor>go run skywire-visor.go and open the UI. The app will appear as not started.
  4. Start the app with the UI and wait for the state to be green.
  5. Stop the app. The procedure will fail with this error: Not Connected., but the state inside the UI will change to red.
  6. 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.

Senyoret1 avatar Jun 12 '23 19:06 Senyoret1

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

0pcom avatar Jun 12 '23 20:06 0pcom

When stoping, the console only shows this: Log

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.

Senyoret1 avatar Jun 12 '23 21:06 Senyoret1