search

beamable / BeamableProduct

The beamable product suite including com.beamable, com.beamable.server, microservice base image, portal, the installer, and build scripts
Other
5 stars 0 forks source link

CLI QA - sometimes `beam project stop` doesn't work #3422

Closed cdhanna closed 4 months ago

cdhanna commented 4 months ago 
PS C:\Users\cdhan\Documents\SAM\Window> beam project ps
CanOfWorms is available prefix=[DESKTOP-MSF6P7B] docker=[True]

Window is available prefix=[DESKTOP-MSF6P7B] docker=[False]

PS C:\Users\cdhan\Documents\SAM\Window> beam project stop --ids Window
stopped Window.

PS C:\Users\cdhan\Documents\SAM\Window> beam project ps
CanOfWorms is available prefix=[DESKTOP-MSF6P7B] docker=[True]

Window is available prefix=[DESKTOP-MSF6P7B] docker=[False]
cdhanna commented 4 months ago

at min, it would be nice to know the process name or something so I could kill it manually. The problem here is that I can't find where the service is running from.

allister-beamable commented 4 months ago

Sounds like the stop command needs a way to detect that the thing you wanted to stop is still "available". If that check is costly in terms of time or compute, then there should be a switch to disable it.

allister-beamable commented 4 months ago

@PedroRauizBeamable raised an interesting point, too: if we can supply the OS with more information about processes (for example, beam.exe), that would allow people to more easily identify things in OS-level process lists and task managers. So like if you look at ps auxww on macOS, you will see a lot of commands with lots of info about their arguments, allowing you to distinguish between, say, different Unity executables.