-
Notifications
You must be signed in to change notification settings - Fork 4
use ProcessHandle
instead of graalvm substitutions
#24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,13 +8,12 @@ trait LockProcess { | |
object LockProcess { | ||
class Default extends LockProcess { | ||
def pid(): Int = | ||
Option((new Pid).get()).map(n => (n: Int)).getOrElse { | ||
sys.error("Cannot get PID") | ||
} | ||
def isRunning(pid: Int): Boolean = | ||
Option((new IsRunning).isRunning(pid)).map(b => (b: Boolean)).getOrElse { | ||
Processes.isRunning(pid) | ||
} | ||
ProcessHandle.current().pid().toInt | ||
def isRunning(pid: Int): Boolean = { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. note that this interface doesnt distinguish "no process with that pid" from "there is a process with that pid but it's not alive". I wonder if there is a practical usecase for forcefully destroying the latter? |
||
val maybeHandle = ProcessHandle.of(pid) | ||
if (maybeHandle.isEmpty) false | ||
else maybeHandle.get.isAlive | ||
} | ||
} | ||
|
||
def default: LockProcess = | ||
|
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this change likely means we could inline/remove the whole
LockProcess
trait, as well as changeInt
toLong
. However, I choose to maintain bincompat instead and just do the minimum here