Update JOB_OBJECT_ALL_ACCESS and OpenJobObject#2095
Conversation
Update `JOB_OBJECT_ALL_ACCESS` value to the most recent one. Update `winapi.OpenJobObject` to accept `inheritHandle` as `bool` as the documentation suggests. Signed-off-by: Maksim An <[email protected]>
|
What is the documentation that suggests we change to passing |
I wanted to make sure that the type matches to what's in the docs: https://learn.microsoft.com/en-us/windows/win32/api/jobapi2/nf-jobapi2-openjobobjectw. The underlying syscall doesn't change, and with the change we won't need to convert |
|
It looks like the syscall code handles this just fine. Just wanted to be clear that in general, Windows |
Update `JOB_OBJECT_ALL_ACCESS` value to the most recent one. Update `winapi.OpenJobObject` to accept `inheritHandle` as `bool`. The underlying syscall stays the same, but this allows cleaner calls from go's perspective as it avoids `bool` to `uint32` casting. Signed-off-by: Maksim An <[email protected]>
Update `JOB_OBJECT_ALL_ACCESS` value to the most recent one. Update `winapi.OpenJobObject` to accept `inheritHandle` as `bool`. The underlying syscall stays the same, but this allows cleaner calls from go's perspective as it avoids `bool` to `uint32` casting. Signed-off-by: Maksim An <[email protected]> (cherry picked from commit 42671b4) Signed-off-by: Kirtana Ashok <[email protected]>
Update `JOB_OBJECT_ALL_ACCESS` value to the most recent one. Update `winapi.OpenJobObject` to accept `inheritHandle` as `bool`. The underlying syscall stays the same, but this allows cleaner calls from go's perspective as it avoids `bool` to `uint32` casting. Signed-off-by: Maksim An <[email protected]> (cherry picked from commit 42671b4) Signed-off-by: Kirtana Ashok <[email protected]>
3 participants
Update
JOB_OBJECT_ALL_ACCESSvalue to the most recent one.Update
winapi.OpenJobObjectto acceptinheritHandleasboolas the documentation suggests.