vim.vm.guest.ProcessManager.ListProcesses
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
When we use vim.vm.guest.ProcessManager.ListProcesses to get the status of a list of PIDs, we get the following attributes:
- name: str
- pid: long
- owner: str
- cmdLine: str
- startTime: datetime
- endTime: Optional[datetime] = None
- exitCode: Optional[int] = None
However, if the exitCode is not 0, we don't have information about stderr/stdout.
Describe the solution you'd like
Add two attributes:
- stderr: str
- stdout: str
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the vim.vm.guest.ProcessManager.ListProcesses entry point and inspect how process attributes are represented in the Python bindings. Check whether stderr and stdout are available from the underlying vSphere API, then identify the existing tests for process listing; done means both attributes are exposed for processes with nonzero exit codes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100