Skip to content
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

Configure Processes with Subsystems #10156

Closed
stuhood opened this issue Jun 24, 2020 · 2 comments
Closed

Configure Processes with Subsystems #10156

stuhood opened this issue Jun 24, 2020 · 2 comments

Comments

@stuhood
Copy link
Member

stuhood commented Jun 24, 2020

There are a few different usecases for per-Process configuration:

  1. temporarily disabling caching (the equivalent of --cache[-scope]-ignore)
  2. configuring timeouts in a uniform way that is transparent to the engine and allows for explaining how to adjust them.
  3. allowing a user to specify additional arguments on a temporary basis (this one is slightly scary, but useful for debugging)

This would involve at least two components:

  • Support for registering scoped-Subsystems in rules.
  • Add an optional Subsystem reference to Process that would be consumed for timeout and cache values.

Open questions:

  • how this relates to Harden PATH setting in pex runs #9760 and Platform/Environment-specific subsystems #7735.
  • whether this is one subsystem or two: preserving the literal --cache[-scope]-ignore syntax would be great, but the other options related to processes are not cache related... ie: --process[-scope]-timeouts.
  • it's possible that a process Subsystem would not be scoped... rather, subclassed. Because an unscoped --process-extra-args would not make sense in general.
@stuhood stuhood added the engine label Jun 24, 2020
@stuhood

This comment has been minimized.

@stuhood
Copy link
Member Author

stuhood commented Sep 18, 2023

The motivation for this issue has probably been removed by per-Environment configuration.

@stuhood stuhood closed this as completed Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants